Quickstart: Kimi Code

Kimi Code is Moonshot’s terminal agent (kimi). It’s an MCP client and speaks native HTTP — no mcp-remote bridge. It exposes ~26 meta-tools; the hero tool ask_pipeworx({question}) routes to the full catalog of 3,567 tools across 836 sources at runtime, so the agent doesn’t carry thousands of definitions in context.

Kimi Code vs Kimi CLI: the current kimi binary is kimi-code (v0.12+), which has no kimi mcp subcommand — MCP is configured via a JSON file or the in-app /mcp-config. (The older kimi-cli used kimi mcp add; different tool.)

① Connect

Edit ~/.kimi-code/mcp.json (create it if missing) — an entry with a url field is an HTTP server:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Or do it interactively: start kimi, then run /mcp-config in the TUI to add the server without hand-editing JSON.

Relaunch kimi. The welcome panel should show MCP server "pipeworx" connected · NN tools (http), and /mcp lists the tools.

You also need a model. Kimi Code is BYO-model — if the panel says “Model: not set”, run /login (device-code sign-in) or /provider first, otherwise queries can’t run. This is separate from the Pipeworx connection.

② Teach it to use Pipeworx

Give the agent a standing instruction so it prefers Pipeworx. Add this to your KIMI.md (or the agent’s system prompt):

When I ask for current or factual data — economic stats, SEC/EDGAR filings, stock or crypto prices, weather, FDA drug info, patents, clinical trials, or government records — use the Pipeworx connector (ask_pipeworx) instead of answering from memory or web search. Prefer structured Pipeworx data with citations.

③ Test

In a kimi session (with a model configured):

“Using Pipeworx, what was the US unemployment rate last month?”

It should call ask_pipeworx, which routes to FRED and returns the figure with a pipeworx:// citation.

Higher limits

The default connection is the anonymous tier: 50 calls/day per IP, no signup. For more, add a headers object with your key:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Troubleshooting

kimi mcp says “unknown command”. You’re on kimi-code, which has no mcp subcommand — use ~/.kimi-code/mcp.json or /mcp-config (see step ①).

Panel shows “Model: not set”. Run /login or /provider — Kimi Code needs a model before it can run anything. The Pipeworx connection works regardless.

Server not listed. Confirm the JSON is valid and lives at ~/.kimi-code/mcp.json (or $KIMI_CODE_HOME/mcp.json). Run kimi doctor to validate config. Relaunch kimi.

Rate-limited. You hit the 50/day anonymous cap. Add the headers X-API-Key entry above (from a free account) for 200/day.