/usr/bin/cat for LLMs
"What if OpenAI’s API docs were a Unix tool?"
llcat is a general-purpose CLI-based OpenAI-compatible /chat/completions caller.
It is like cURL or cat for LLMs: a stateless, transparent, explicit, low-level, composable tool for scripting and glue.
Conversations, keys, servers and other configurations are explicitly specified each execution as command line arguments. This makes building things with llcat simple and direct.
There is no caching or state saved between runs. Everything gets surfaced and errors are JSON parsable.
List the models on OpenRouter:
uvx llcat -u https://openrouter.ai/api -m
llcat can:
- Use local or remote servers, authenticated or not.
- Store conversation history optionally, as a JSON file.
- Pipe things from stdin and/or be prompted on the command line.
- Do tool calling using the OpenAI spec and MCP STDIO servers.
- List and choose models, system prompts, and add attachments.
llcat's basic CLI parameters are also compatible with Simon Willison's llm.
Because conversations, models and servers are decoupled, you can easily mix and match them at any time.
Here's one conversation, hopping across models and servers.
Start a chat with Deepseek:
$ llcat -u https://openrouter.ai/api \
-m deepseek/deepseek-r1-0528:free \
-c /tmp/convo.txt \
-k $(cat openrouter.key) \
"What is the capital of France?"
Continue it with Qwen:
$ llcat -u https://openrouter.ai/api \
-m qwen/qwen3-4b:free \
-c /tmp/convo.txt \
-k $(cat openrouter.key) \
"And what about Canada?"
And finish on the local network:
$ llcat -u http://192.168.1.21:8080 \
-c /tmp/convo.txt \
"And what about Japan?"
Since the conversation goes to the filesystem as easily parsable JSON you can use things like inotify or fuse and push it off to a vector search backend or modify the context window between calls.
llcat's explicit syntax means lots of things are within reach.
For instance simple wrappers can be made custom to your workflow.
Here's a way to store state with environment variables to make invocation more convenient:
llc() { llcat -m "$LLC_MODEL" -u "$LLC_SERVER" -k "$LLC_KEY" "$@" }
llc-model() { LLC_MODEL=$(llcat -m -s "$LLC_SERVER" -k "$LLC_KEY" | fzf) }
llc-server() { LLC_SERVER=$1 }
llc-key() { LLC_KEY=$1 }And now you can do things like this:
$ llc-server http://192.168.1.21:8080
$ llc "write a diss track where the knapsack problem hates on the towers of hanoi"
There's no configuration files to parse or implicit states to manage.
A conversation interface is also quick:
#!/usr/bin/env bash
# We pick a file for the conversation or allow a user to pass it in with a CONV environment variable
conv=${CONV:-$(mktemp)}
echo -e " Using: $conv\n"
# Show the previous conversation if there is any, stylize it with streamdown
jq -r '.[] | "\n**\(.role)**: \(.content)"' $conv | sd
# Read prompts in a loop
while read -E -p " >> " query; do
# Take the command line arguments of the shell script, pass them to llcat
llcat -c $conv "$@" "$query" |& sd
echo
doneSo now instead of
llcat -u http://myserver -k mykey -m model
Our conversation loop can be invoked like
conversation.sh -u http://myserver -k mykey -m model
Adding additional features is trivial.
Running the same thing on multiple models and assessing the outcome is straight forward. Here we're using ollama
pre="llcat -u http://localhost:11434"
for model in $($pre -m); do
$pre -m $model "translate 国際化がサポートされています。to english" > ${model}.outcome
doneYou can use patterns like that also for testing tool calling completion.
If an error happens contacting the server, you get the request, response, and a non-zero exit.
Try this to see what that looks like
uvx llcat -u fakecomputer
The examples directory contains this music playing tool listing the contents of this album:
$ llcat -u http://127.1:8080 -tf tool_file.json -tp tool_program.py "what mp3s do i have in my ~/mp3 directory"
{"level": "debug", "class": "toolcall", "message": "request", "obj": {"id": "iwCGjcRic8GAFB2jUvBUOeF9NNrldfxz", "type": "function", "function": {"name": "list_mp3s", "arguments": {"path":"~/mp3"}}}}
{"level": "debug", "class": "toolcall", "message": "result", "obj": ["Elektrobopacek - Towards the final Battle.mp3", "Elektrobopacek - Escape the Labyrinth.mp3", "Elektrobopacek - Journey to the misty Lands.mp3", "Elektrobopacek - Mistral Forte.mp3", "Elektrobopacek - Leaving Spaceport X-19.mp3", "Elektrobopacek - Dracula Rising.mp3"]}
Here are the MP3 files in your `~/mp3` directory:
1. **Elektrobopacek - Towards the final Battle.mp3**
2. **Elektrobopacek - Escape the Labyrinth.mp3**
3. **Elektrobopacek - Journey to the misty Lands.mp3**
4. **Elektrobopacek - Mistral Forte.mp3**
5. **Elektrobopacek - Leaving Spaceport X-19.mp3**
6. **Elektrobopacek - Dracula Rising.mp3**
Would you like to play any of these? Just share the filename, and I can play it for you! 🎵In this example you can see how nothing is hidden so if the model makes a mistake it is immediately identifiable.
The debug JSON objects are sent to stderr so routing it separately is trivial.
MCP can be simple with simple tools. There's one included here. mcpcat is a 22 line Bash script.
Here is an example of it in use:
$ mcpcat init list | \
uv run python -m my-server | \
jq .Let's say there's a calculator mcp, you can do something like
$ mcpcat init call calculate '{"expression":"2+2"}' | \
uv run python -m mcp_server_calculator \
jq .The beauty here is you can see the Emperor's new clothes up close. Simply omit the pipe.
$ mcpcat init call calculate '{"expression":"2+2"}'
{"jsonrpc":"2.0","id":4,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"mcpcat","version":"1.0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"calculate","arguments":{"expression":"2+2"}}}That's all the STDIO Transport is.
There's ways of doing the network transports with this script as well. All you need is the appropriate network tools and compose away.
Now it's your turn.
usage: llcat [-h] [-c CONVERSATION] [-m [MODEL]] [-sk KEY] [-su SERVER] [-s SYSTEM]
[-tf TOOL_FILE] [-tp TOOL_PROGRAM] [-a ATTACH] [--version]
[user_prompt ...]
positional arguments:
user_prompt Your prompt
options:
-h, --help show this help message and exit
-c, --conversation CONVERSATION
Conversation history file
-m, --model [MODEL] Model to use (or list models if no value)
-sk, --key KEY Server API key for authorization
-su, -u, --server SERVER
Server URL (e.g., http://::1:8080)
-s, --system SYSTEM System prompt
-tf, --tool_file TOOL_FILE
JSON file with tool definitions
-tp, --tool_program TOOL_PROGRAM
Program to execute tool calls
-a, --attach ATTACH Attach file(s)
--version show program's version number and exitWe're excited to see what you build.
Brought to you by DA`/50: Make the future obvious.