Skip to main content
Add Firecrawl’s Search, Scrape, and other web tools to Kimi Code CLI through the hosted MCP server.

Quick setup

Create a Firecrawl API key, then add this to ~/.kimi-code/mcp.json (or .kimi-code/mcp.json in a project):
To keep the key out of the file, export it and reference the variable instead of headers:
You can also add the server interactively with /mcp-config. Start a new Kimi Code session, run /mcp, and confirm that firecrawl is connected and its tools, such as firecrawl_search and firecrawl_scrape, are listed. To sign in with your browser instead of an API key, use https://mcp.firecrawl.dev/v2/mcp-oauth as the URL with no headers, then run /mcp-config login firecrawl. See For Humans.

Try it

Troubleshooting

  • Tools do not appear: MCP servers load when a session starts, so open a new session after editing mcp.json. A server added mid-session only joins later sessions.
  • Server does not connect: run /mcp to see the status, then check the URL and that the API key is correct. With bearerTokenEnvVar, the variable must be set in the shell that starts kimi.
  • Project-level config is ignored: untrusted folders keep project .kimi-code/mcp.json servers disabled. Trust the folder, or set KIMI_CODE_TRUST_WORKSPACE=1 for headless runs.
  • Prefer a local server: Kimi Code can also run npx -y firecrawl-mcp with FIRECRAWL_API_KEY in env. See Run locally.