The mcp table in its own .mcp.toml

What it does

Moves the mcp table out of ganja.toml into a file of its own, .mcp.toml, so the file ganja mcp add writes is separate from the file a person comments by hand, and keys hoisted out of the table to avoid colliding with a server name can return to it.

Source

ganja-code-6acv (split the mcp table into .mcp.toml).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README's only word on tools is "permission-gated tools" (README.md:6); it says nothing about MCP.
• Today's terminal users: ganja mcp add edits ganja.toml through toml_edit so comments survive (D483, D536), and tool_defer_threshold sits at the top level to avoid colliding with a server of that name (D462).
• Evidence: It changes the shape of the configuration, which is hard to take back. The bead lists four questions to answer before any code: which tiers .mcp.toml is discovered in and how it merges with a table still in the main file; additive or a clean cut; what ganja mcp add writes when neither file exists; whether the schema splits with it.

Depends on

Nothing.

Verdict

• Verdict: do
• Size: S — one commit, no plan.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #43

Theme: #55

Start by inspecting the current ganja mcp add handling of ganja.toml through toml_edit, with context from README.md. Resolve how .mcp.toml is discovered and merged, whether the change is additive or a clean cut, what happens when neither file exists, and whether the schema splits. Done means the chosen configuration behavior and command output are implemented consistently.