Tachibot MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 387 installs a week from npm. Last commit 20 Oct 2026.
Multi-model AI orchestration with 31 tools, YAML workflows, and 5 token-optimized profiles.
We read the source, 7 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/postinstall-hint.js || true
try { return fs.statSync(path.join(dir, bin + ext)).isFile(); } catch { return false; }
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tachibot-mcp -e 'PERPLEXITY_API_KEY=<PERPLEXITY_API_KEY>' -e 'GROK_API_KEY=<GROK_API_KEY>' -e 'OPENAI_API_KEY=<OPENAI_API_KEY>' -- npx -y tachibot-mcp
{
"mcpServers": {
"tachibot-mcp": {
"command": "npx",
"args": [
"-y",
"tachibot-mcp"
],
"env": {
"GROK_API_KEY": "<GROK_API_KEY>",
"OPENAI_API_KEY": "<OPENAI_API_KEY>",
"PERPLEXITY_API_KEY": "<PERPLEXITY_API_KEY>"
}
}
}
}
[mcp_servers.tachibot-mcp]
command = "npx"
args = ["-y", "tachibot-mcp"]
env = { PERPLEXITY_API_KEY = "<PERPLEXITY_API_KEY>", GROK_API_KEY = "<GROK_API_KEY>", OPENAI_API_KEY = "<OPENAI_API_KEY>" }
{
"mcpServers": {
"tachibot-mcp": {
"command": "npx",
"args": [
"-y",
"tachibot-mcp"
],
"env": {
"GROK_API_KEY": "<GROK_API_KEY>",
"OPENAI_API_KEY": "<OPENAI_API_KEY>",
"PERPLEXITY_API_KEY": "<PERPLEXITY_API_KEY>"
}
}
}
}
{
"servers": {
"tachibot-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tachibot-mcp"
],
"env": {
"GROK_API_KEY": "<GROK_API_KEY>",
"OPENAI_API_KEY": "<OPENAI_API_KEY>",
"PERPLEXITY_API_KEY": "<PERPLEXITY_API_KEY>"
}
}
}
}
Put your own values in place of
<PERPLEXITY_API_KEY> (Perplexity API key for web search, research, and reasoning (https://www.perplexity.ai/settings/api)), <GROK_API_KEY> (Grok/xAI API key for code analysis, debugging, and architecture (https://console.x.ai/)), <OPENAI_API_KEY> (OpenAI API key for GPT-5 analysis and comparison (https://platform.openai.com/api-keys)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GOOGLE_API_KEY (Google Gemini API key for brainstorming and code/text analysis (https://aistudio.google.com/apikey)), OPENROUTER_API_KEY (OpenRouter API key for Qwen3 Coder and other models), TACHIBOT_PROFILE (Tool profile selection: minimal, research_power, code_focus, balanced, or full (default: balanced)).
Multi-model AI orchestration MCP server with code review, compare, and debate tools.
Self-improving AI workflows with backtesting, prompt optimization, and scheduling
Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows
AI agent marketplace for automated employees, workflows, skills, and tool orchestration.
Multi-step workflow orchestration for VMware MCP skills with approval gates and rollback.
Multi-step workflow orchestration for VMware MCP skills with approval gates and rollback.
MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration
Manage tasks, projects, roadmaps, files, meetings, and team workflows with AI tools.
Answers built from our own checks of this server.