Loading documentation...
Get TachiBot MCP running in minutes. Install via npm and configure your API keys.
Detects your API keys and clients, then prints the exact config for Claude Code and Claude Desktop — never writes or echoes keys:
The fastest path — no global install needed:
Then verify with /mcp. Add --env flags only for the keys you have.
Edit your Claude Desktop configuration file:
Add TachiBot to the MCP servers (API keys go in the env block):
There are two ways to configure API keys (pick one):
Pass keys when adding the server — they land in the MCP config for you:
Add API keys directly in your MCP client config (~/.claude.json for Claude Code,claude_desktop_config.json for Claude Desktop):
When the same key is set in multiple places, this is the priority order (highest wins):
.env in the TachiBot install directory (source installs / development — loaded with override)env block (~/.claude.json / claude_desktop_config.json) — the normal path for npm/npx installsSimplify setup with one API key! Enable Gateway Mode to route GPT-5.5, Gemini, and Grok through OpenRouter.
You don't need all API keys! Only add keys for the tools you want to use. Check the Tools page to see which tools require which keys.
Restart your Claude application (Claude Desktop or Claude Code) and check that:
mcp__tachibot-mcp__focus are availableTachiBot works with both Claude Code (CLI with file system access) and Claude Desktop (GUI chat interface).
You're all set! Here's what to do next