On this page
Kater CLI Run Kater's services
kater serve
Starts the Kater MCP server, which gives an AI agent Kater's tools.
You seldom run it by hand: your agent’s MCP client starts it from its settings. Platform admins run the hosted server with --mode remote.
Examples
# Serve the local copy in this folder to one agent over stdio, as kater agent sets it upkater serve --kater-root .# Serve several local agents at one address, behind the token in KATER_MCP_TOKENkater serve --transport http --port 8765# Serve without keeping compile results on diskkater serve --no-cache# Run the hosted server, behind PropelAuth sign-inkater serve --mode remoteOptions
It also takes the global options --json, --kater-root, --scope and --help.
Who runs it
- Your agent, over stdio.
kater agent claudeandkater agent codexwrite MCP settings for your local copy. They runkater serve --kater-root .. The agent then starts the server. Its log goes to stderr, since stdout carries the protocol. - Several local agents, over HTTP. Set
KATER_MCP_TOKENfirst: the server does not start without it. It prints{"serving": "http://127.0.0.1:<port>/mcp"}once its port is open. It stops when the process that started it exits. - Platform admins, for the hosted server.
--mode remoteserves Streamable HTTP at/mcp. It reads its address and sign-in settings from environment variables, such asKATER_MCP_PORT, which is8000unless set.--transport,--portand the cache options apply only to local mode.
Agents and the Files terminal cannot run kater serve. See MCP server and tools.
Your open pages
When you signed in with kater login, a local server can see your open Kater pages. Without a sign-in, its tools say that they cannot. Run kater login, then start kater serve again.
Settings
Each option can also come from an environment variable, such as KATER_SERVE_MODE. A flag wins over it. See Configuration.
Editor intelligence, such as completions and diagnostics, comes from a separate server, kater-lsp. See VS Code extension.