MCP servers

MCP servers give a coding agent tools it doesn't have on its own: search a library's current docs, look through code on GitHub, read your Sentry issues. You set them up once in taiku, and the agents you start with taiku agent --local get them: Claude Code, Codex, and the other agents that can reach MCP servers over HTTP. taiku agent tells you when the one you started can't.

Turn on a suggested serverCopy Anchor Link

taiku mcp list

Besides anything you've added, the list shows a few servers taiku suggests. They stay off until you turn one on:

taiku mcp enable context7
taiku mcp enable sentry
taiku mcp auth sentry

taiku mcp auth opens the server's sign-in page and waits for you to come back. On a machine with no browser, add --no-browser and open the printed link anywhere that can reach this machine.

Add your ownCopy Anchor Link

A remote server is a URL:

taiku mcp add linear https://mcp.linear.app/mcp
taiku mcp auth linear

Most remote servers sign you in with OAuth, and taiku registers itself with the server the first time, so there's usually nothing to set up in advance. If the server gave you a client ID (and maybe a secret), pass them instead:

taiku mcp add acme https://mcp.acme.dev --client-id taiku-desktop --scope "read write"

A server that takes an API key rather than a sign-in gets the key in a header. Write {env:NAME} to read it from your environment each time, so the key never sits in taiku's config:

taiku mcp add context7 https://mcp.context7.com/mcp --no-oauth \
  -H 'CONTEXT7_API_KEY={env:CONTEXT7_API_KEY}'

A local server is a command taiku starts for you:

taiku mcp add fs -- npx -y @modelcontextprotocol/server-filesystem ~/notes

If the command's runtime isn't installed, taiku says which one: "uvx is not on PATH: this server needs uv".

Choose tools per agentCopy Anchor Link

taiku mcp disable sentry --agent codex keeps Sentry away from Codex and leaves it on for everyone else. For finer control, name tools in the config. A tool's full name is the server's name and the tool's, joined by _, and * and ? match any run of characters or any one:

{
  "mcp": {
    "sentry": { "type": "remote", "url": "https://mcp.sentry.dev/mcp" }
  },
  "tools": { "sentry_*": false },
  "agent": {
    "claude": { "tools": { "sentry_*": true, "sentry_update_issue": false } }
  }
}

Here only Claude gets Sentry, and not the tool that changes an issue. An agent's own rule beats the global one, and the more specific pattern wins. A tool that's filtered out is missing from the agent's list and refused if it asks for it anyway.

The file is mcp.json in taiku's config folder (taiku mcp list prints where). It uses the same keys as OpenCode's mcp block, so a server you already set up there can be copied across as it is.

When a server doesn't workCopy Anchor Link

taiku mcp debug sentry --agent claude

This walks each step and says how it went: whether you're signed in and when the sign-in expires, what the server says about signing in, how long it took to connect, and each tool, marked where the agent's rules hide it. When a server wants you to sign in again, taiku agent also says so before the agent starts.

Agents that run on taikuCopy Anchor Link

An agent you set up in the dashboard runs on taiku rather than on your machine, so its servers live on its page under Connectors, not in mcp.json. The suggested servers are listed there too, and Add puts one on that agent.

For your own, Add a connector takes the URL and how it signs in: its headers (for a server that takes an API key), OAuth, or OAuth with a client ID you registered with the server. Once it's added, Sign in takes you to the server's sign-in page and brings you back to the agent. The row says whether it's signed in, and Sign out asks the server to cancel the tokens.

Tools takes the same patterns as the config file, one per line, without the server's name in front: delete_*=off hides every tool whose name starts with delete_.

What the agent seesCopy Anchor Link

The agent never gets your sign-in. taiku holds it, refreshes it when it runs out, and passes the agent's calls on. The agent talks to taiku, on the machine it runs on, with a key made for that one run, so a token doesn't end up in the agent's settings, its logs or the conversation. That holds for agents on taiku too: their sign-ins are stored encrypted, and a tool you turned off is refused even if the agent asks for it by name.

taiku mcp logout sentry signs you out and asks the server to cancel the tokens; taiku mcp remove sentry does the same and forgets the server.