TachiBot MCP

• Tool descriptions no longer name-drop model versions. 19 descriptions were rewritten to name the provider and the task instead of pinned strings like "GPT-5.2", "Kimi K3" or "424B MoE" — those silently rot on every model bump and then actively mislead the routing model. Two were outright wrong: openai_reason and openai_search advertised "GPT-5.2" while the code calls the current OpenAI flagship tier.
• grok_search finally says why to pick it. Its entire description was "Web search" — no way to choose it over the four other search tools. It now states its live X/news grounding edge and cross-references grok_search_lite as the cheaper path. The five OpenRouter reasoners (deepseek_reason, glm_reason, stepfun_reason, ernie_reason, qwen_reason) likewise differed only by vendor trivia; each now carries an actual routing rule for when to pick it.
• Claude Desktop manifest corrected — it advertised 65 tools (actual: 66), omitted the heavy_coding profile from the TACHIBOT_PROFILE help, and its OPENAI_API_KEY hint claimed that key powers the Qwen and QwQ tools (those route via OpenRouter).
• Packaging no longer breaks the working tree. scripts/package-extension.sh ran npm install --production, pruning devDependencies and leaving tsc unable to build afterward. It now restores the full dependency tree when it finishes.
• The server introduced itself as v2.0.0. serverInfo.version was hardcoded from a 12-tool era ~28 minor versions ago, so Claude Desktop's connector panel misidentified every install. It now reads the real version from package.json. The /setup wizard's profile sizes were stale in the same way and now match the six real profiles.
• Correction to v2.30.0: grok_search_lite is not broken, and is staying. That release claimed grok-4.3 "does not invoke web search either" — which would have made the cheap search tier pointless. Re-probed Aug 15 asking today's date: grok-4.3 ran 2 web searches and returned a citation in 10.4s; grok-4.6 did the same in 36.4s. Lite is grounded, cheaper, and 3–4x faster — prefer it for high-volume lookups. grok-4.5 is still the one that doesn't ground. The cheap tier now has its own grounding test, since nothing previously covered it.
• No tools added or removed — the count stays 66.

• grok_search was not searching. It ran on grok-4.5, which never invokes the web_search tool on xAI's Agent Tools API — so it answered from training data while still rendering a source footer and a "Search used up to N sources" cost line computed locally from max_search_results, not from real usage. Probed Aug 14: asked today's date, grok-4.5 replied "October 10, 2025" with zero web_search_call entries; grok-4.6 replied correctly with two search calls and a citation. grok_search now runs grok-4.6 (same $2/$6 and 500K context as 4.5). The regression test asserts grounding — a web_search_call and ≥1 annotation — never the answer text, because a plausible ungrounded answer is precisely what hid this.
• Correction to the v2.27.0 note below: grok_search_lite never ran on grok-4-1-fast at $0.20/$0.50. xAI retired that id and silently served grok-4.3 — HTTP 200, the swap disclosed only in the response body's model field, so nothing threw and no fallback fired. The advertised "~10x cheaper" was really ~1.6x.
• 13 console.log calls were corrupting the MCP protocol stream. stdout is the JSON-RPC channel on a stdio server; diagnostics now go to stderr, guarded by a test that also rejects console.info, console.debug and process.stdout.write.
• create_workflow silently destroyed existing workflow files — the existence check guarded the directory, not the file. It now refuses to clobber unless overwrite: true, and reports the real .tachibot/workflows/ path instead of .tachi/workflows/.
• Eight prompt maps injected the literal string "undefined" into system prompts for any unrecognised approach/task, because the || fallback sat inside the index. Fixed across grok_reason, grok_code, kimi_thinking, qwen_reason, deepseek_reason, glm_reason, stepfun_reason, ernie_reason.
• Workflow steps ran the wrong model — the qwen_algo step called QwQ-32B with a generic prompt instead of Qwen3.8-Max, and qwq_reason lost its 4-persona deliberation entirely. Both now delegate to the real tools. Separately, planner_maker's qwen_coder step sent a parameter the schema rejects, so every execution of it failed validation.
• Test suite 130 → 158. The live search probe is now opt-in behind RUN_LIVE_TESTS=1, so an ordinary npm test no longer makes a billed API call.

• Qwen3.8 Max (Aug 3, qwen/qwen3.8-max) — Alibaba's new flagship, GA the same day, now powers qwen_algo, qwen_reason, and the qwen_reason juror. 1M context (up from 262K), multimodal (text+image+video in), and the first Qwen exposing configurable reasoning effort. $2/$6 per M.
• Measured on a range-query algorithm problem, 3.8 Max was the only one of five Qwen candidates to surface both the offline-vs-online tradeoff and the strict-inequality-with-duplicates edge case. The outgoing qwen3-235b-a22b-thinking-2507 was correct but shallow; qwen3.7-max cost 1.6x for twice the wall time; qwen3-max-thinking was rejected outright — it returns zero reasoning tokens.
• Effort is pinned to medium, deliberately. This model's default effort behaves like high: 302s and $0.09 on a single qwen_algo call. At medium the same call answers at equal depth in 18–48s for $0.006–0.018 — cheaper and 3.5x faster than the model it replaces, which took 169s and $0.036 for a shorter answer. low starts dropping alternatives and is not used.
• reasoning_effort pass-through for OpenRouter — callOpenRouter now forwards the parameter; OpenRouter drops it for models that don't list it, so the quota fallback chain (3.8 Max → 3.7 Max → 235B Thinking) stays safe. Qwen3.8/3.7-Max also join the 600s extended-timeout bucket.
• qwen_coder, qwen_competitive, testgen stay on Qwen3-Coder-Next — it is coding-specialized and ~16x cheaper ($0.12/$0.80); 3.8 Max is the reasoning tier, not the codegen tier.

• Kimi K3 (Jul 16, moonshotai/kimi-k3) now powers every Kimi tool, the kimi juror, and the Kimi seat on diff_review. 2.8T open-weight MoE — the largest open model shipped — with a 1M context (up from 262K), native multimodal input, and long-horizon agentic coding that beats Opus 4.8 and GPT-5.5 on coding/agent benchmarks. Note the price: $3/$15 per M, 4x K2.7-Code — K2.7-Code stays as the automatic fallback (K3 → K2.7-Code → K2.6).
• Gemini 3.6 Flash (Jul 21, gemini-3.6-flash) is the new search/workhorse tier behind gemini_search — 1M context at $1.50/$7.50, down from $9 output, and ~17% fewer output tokens than 3.5 Flash. Flash-Lite moves to gemini-3.5-flash-lite ($0.30/$2.50).
• Everything else re-verified, unchanged — a full provider audit (Jul 26) confirms GPT-5.6, Grok 4.5, DeepSeek V4 Pro, GLM-5.2, MiniMax M3, StepFun 3.7, ERNIE 4.5 VL, Qwen Coder-Next and Perplexity Sonar are all still the newest available. Gemini 3.1 Pro remains the reasoning/judge default: Google shipped three models on Jul 21 and skipped 3.5 Pro. xAI's staged rollout finished (EU access Jul 17), so the grok-4.3 fallback is now quota/region insurance rather than a rollout workaround.

• Grok 4.5 (Jul 8 flagship, "Opus-class") now powers all Grok tools, with automatic fallback to grok-4.3 while xAI's region-staged rollout completes (EU mid-July) — tools keep working everywhere, and 4.5 activates by itself.
• grok_search_lite (new tool, 65 total) — the same Grok live search on grok-4-1-fast ($0.20/$0.50, 2M ctx), ~10x cheaper than grok_search. Use it for high-volume lookups and jury/council fan-outs.
• GPT-5.6 tiers — openai_* tools move to gpt-5.6-sol (flagship, same $5/$30 as 5.5 but stronger), terra for code (5.5-level at half price), luna for explanations ($1/$6). The $30/$180 gpt-5.5-pro tier is replaced by sol + reasoning effort; a permission fallback (sol → terra → 5.5) covers org-gated accounts.

• /test and /audit skills (19 skills total) — /test generates runnable tests via testgen; /audit runs an OWASP/CWE security review via security_review.
• Skill install in the wizard — tachibot init now offers to install Claude Code skills with a per-skill skip choice ([Enter]=all · [s]=choose which to skip · [n]=none). Skills are opt-in — postinstall no longer writes to ~/.claude silently (npm run install-skills still installs all non-interactively).
• Fixes — the one-click .mcpb extension now points at a valid entry point (was broken) and tracks the package version; tachibot init exits cleanly on non-interactive/CI stdin instead of hanging.

• refine_prompt (new tool) — opt-in prompt improver on a cheap/fast model: raw query → goal-first brief + what changed + open questions. Never auto-fires, never executes anything — you review, then use the brief. In Claude Code, /prompt refine presents the open questions as clickable choices and merges your answers into a final brief.
• Curated technique list — list_prompt_techniques now defaults to the ~9 core techniques that still help 2026 reasoning models (output contracts like scot, pre_mortem, bdd_spec); all=true for the full 31.
• technique="auto" — preview_prompt_technique recommends the right technique for your task, with reasons. Ask tachi "improve my prompt" for the symptom-based menu.

• tachibot init (new CLI wizard) — detects your API keys and clients, prints the exact config for Claude Code and Claude Desktop. Never writes or echoes keys.
• One-click Claude Desktop install — download the .mcpb from the latest release and double-click. No JSON editing.
• doctor — shows which keys are set, which tools are visible vs hidden and why, and what to try first.

• debug_triage — ranked root-cause hypotheses with the cheapest discriminating check for each (Grok 4.3)
• spec_writer — loose request → reviewable spec: user stories, Given/When/Then, out-of-scope, open questions (GPT-5.5)
• diff_review / plan_critique / testgen / security_review — multi-model diff review, adversarial plan red-team, test generation, OWASP/CWE audit
• Skills: /review, /redteam, /spec, /triage, /setup

• focus orchestration screen: 37 lines of repeated scaffolding → 10 focused lines
• npm test exits 0 again (uncancelled race timers leaked past Jest teardown)
• GPT-5.5 high-effort reasoning no longer cut off at 3 minutes (timeout 180s → 600s)

TachiBot ships with 19 slash commands for Claude Code. These orchestrate the tools into powerful workflows:

Skills automatically adapt to your configured API keys. Even with just 1-2 providers, all skills work.

Getting started? Type /tachi to see what's available.

• 65 AI Tools across 12 providers — Perplexity, Grok, GPT-5, Gemini, Qwen, Kimi, MiniMax, DeepSeek, GLM (Zhipu), StepFun, ERNIE (Baidu), plus free local models (Ollama / LM Studio / llama.cpp / vLLM)
• Gemini 3.6 Flash (gemini-3.6-flash, GA Jul 21 2026) — Flash/search tier; reasoning default stays gemini-3.1-pro-preview (Google has still not shipped a 3.5 Pro)
• Multi-Model Council — planner_maker synthesizes plans from 5+ models into bite-sized TDD steps
• Smart Routing — Automatic model selection for optimal results
• OpenRouter Gateway — Optional single API key for all providers

• YAML-Based Workflows — Multi-step AI processes with dependency graphs
• Prompt Engineering — 85 research-backed techniques (including SCoT, ReAct, Reflexion, Chain-of-Note, Spotlighting)
• Verification Checkpoints — 50% / 80% / 100% with automated quality scoring
• Parallel Execution — Run multiple models simultaneously

• Claude Code — First-class support
• Claude Desktop — Full integration
• Cursor — Works seamlessly
• TypeScript — Fully typed, extensible

npm install -g tachibot-mcp

npx -y -p tachibot-mcp tachibot init

Detects your keys and clients, then prints the exact config for Claude Code and Claude Desktop.

claude mcp add tachibot -- npx -y -p tachibot-mcp tachibot

Then verify with /mcp. Add API keys with --env, e.g. --env OPENROUTER_API_KEY=sk-or-xxx --env PERPLEXITY_API_KEY=pplx-xxx.

One-click (easiest): download tachibot-mcp.mcpb from the latest release and double-click it — Claude Desktop installs the extension with no JSON editing. Add your API keys when prompted (or later via the extension settings).

Gateway Mode (Recommended) — 2 keys, all providers:

{
  "mcpServers": {
    "tachibot": {
      "command": "tachibot",
      "env": {
        "OPENROUTER_API_KEY": "sk-or-xxx",
        "PERPLEXITY_API_KEY": "pplx-xxx",
        "USE_OPENROUTER_GATEWAY": "true"
      }
    }
  }
}

Direct Mode — One key per provider:

{
  "mcpServers": {
    "tachibot": {
      "command": "tachibot",
      "env": {
        "PERPLEXITY_API_KEY": "your-key",
        "GROK_API_KEY": "your-key",
        "OPENAI_API_KEY": "your-key",
        "GOOGLE_API_KEY": "your-key",
        "OPENROUTER_API_KEY": "your-key"
      }
    }
  }
}

Get keys: OpenRouter | Perplexity

See Installation Guide for detailed instructions.

perplexity_ask · perplexity_reason · grok_search · grok_search_lite · openai_search · gemini_search

grok_reason · openai_reason · qwen_reason · qwq_reason · kimi_thinking · kimi_decompose · deepseek_reason · glm_reason · stepfun_reason · ernie_reason · planner_maker · planner_runner · list_plans · spec_writer

kimi_code · grok_code · grok_debug · qwen_coder · qwen_algo · qwen_competitive · deepseek_algo · minimax_code · minimax_agent · testgen · debug_triage

gemini_analyze_text · gemini_analyze_code · gemini_judge · jury · diff_review · plan_critique · gemini_brainstorm · openai_brainstorm · openai_code_review · openai_explain · grok_brainstorm · grok_architect · security_review · kimi_long_context

think · nextThought · focus · tachi · doctor · usage_stats

workflow · workflow_start · continue_workflow · list_workflows · create_workflow · visualize_workflow · workflow_status · validate_workflow · validate_workflow_file

list_prompt_techniques · preview_prompt_technique · execute_prompt_technique · refine_prompt

local_query — any OpenAI-compatible local server (Ollama / LM Studio / llama.cpp / vLLM). Zero-cost, offline, private; also available as the local jury juror (hermes is accepted as a legacy alias). Runs whatever LOCAL_LLM_MODEL points at — e.g. a Nous Hermes build (ollama pull hermes3). Note the Hermes agent itself is model-agnostic — it runs on 300+ backends (GPT, Claude, Gemini, DeepSeek, or self-hosted Ollama/vLLM) — so "Hermes" was never a guarantee of distinct weights.

• Challenger — Critical analysis with multi-model fact-checking
• Verifier — Multi-model consensus verification
• Scout — Hybrid intelligence gathering

// Create a plan with multi-model council
planner_maker({ task: "Build a REST API with auth and tests", mode: "start" })
// → Grok searches → Qwen analyzes → Kimi decomposes → GPT critiques → Gemini synthesizes

// Execute with checkpoints
planner_runner({ plan: planContent, mode: "step", stepNum: 1 })
// → Automatic verification at 50%, 80% (kimi_decompose), and 100%

kimi_decompose({
  task: "Migrate monolith to microservices",
  depth: 3,
  outputFormat: "dependencies"
})
// → Structured subtasks with IDs, parallel flags, acceptance criteria

kimi_code({
  task: "review",
  code: "function processPayment(amount, card) { ... }",
  language: "typescript"
})
// → SWE-Bench 76.8% quality analysis

focus({
  query: "Design a scalable event-driven architecture",
  mode: "deep-reasoning",
  models: ["grok", "gemini", "kimi"],
  rounds: 5
})

• Full Documentation
• Installation Guide
• Configuration
• Tools Reference
• Workflows Guide
• API Keys Guide
• Focus Modes

• Claude Code Setup
• Claude Desktop Setup
• Both Platforms

Contributions welcome! See CONTRIBUTING.md for guidelines.

• Report Issues
• Request Features