MCP servers

kanade has a read-only MCP tab in the right rail. It surfaces every Model Context Protocol server you’ve registered, project by project, so you can see at a glance what tools Claude has available in this session.

Where the data comes from

kanade reads three locations, in order:

1. ~/.claude.json — your user-scope MCP configuration.
2. The active project’s mcpServers field (if any).
3. Every .mcp.json checked into projects under your active workspace.

Entries are normalized across the two transport types (stdio and HTTP), and environment-variable keys are shown but values are never displayed.

What’s shown for each server

• Name — the registered identifier.
• Transport — stdio or http.
• Command + args (stdio) or URL (http).
• Env var keys — just the names. Values stay hidden.
• Source — which file the entry came from. Useful when you’re debugging a project’s local .mcp.json vs. your user-scope ~/.claude.json.

What kanade does NOT do

• It does not edit your MCP configuration. Use Claude Code’s CLI or your editor.
• It does not test connectivity. The panel reflects configuration only.
• It does not surface env-var values. Even briefly, even in dev tools.

If you want to add or remove an MCP server, edit the relevant JSON file directly. kanade’s MCP tab will pick it up on next reload.