Problem
MCP support today is one-directional: SproutGit runs its own per-workspace MCP server and can write its connection config into known CLI clients (Claude Code, Gemini, Codex, Cursor, Kiro — McpSection.tsx). But users can't register their own MCP servers (Linear, Sentry, a company-internal server, a database inspector…), and integrated ACP sessions receive mcpServers: [] (chat.ts) — so whatever MCP stack a user relies on in one agent is invisible to every other agent.
Proposal
Make MCP configuration agent-agnostic: configure servers once in SproutGit, and every agent gets them.
Trust
A stdio MCP server is arbitrary command execution. Registry entries created by the user in Settings are user-authored (like local hooks — always trusted). Anything imported (from a repo file or a shared JSON) must go through explicit confirmation before first launch, mirroring the hooks trust model. Never auto-start an MCP server whose definition arrived via git pull.
Related: #145 (SproutGit's own tools), #143 (roster), #99 (MCP surface).
Problem
MCP support today is one-directional: SproutGit runs its own per-workspace MCP server and can write its connection config into known CLI clients (Claude Code, Gemini, Codex, Cursor, Kiro —
McpSection.tsx). But users can't register their own MCP servers (Linear, Sentry, a company-internal server, a database inspector…), and integrated ACP sessions receivemcpServers: [](chat.ts) — so whatever MCP stack a user relies on in one agent is invisible to every other agent.Proposal
Make MCP configuration agent-agnostic: configure servers once in SproutGit, and every agent gets them.
command,args,env) or HTTP (URL + headers) — with global defaults and per-workspace enable/disable.newSessioncall passes the enabled registry entries (plus SproutGit's own server, Wire SproutGit's MCP server into every integrated agent session #145) via themcpServersparameter. Any ACP agent — including ad-hoc roster agents (Agent roster + ad-hoc ACP agents: configure any ACP-speaking CLI, not just known presets #143) — gets the full stack with zero per-agent setup.safeStorage, same rules as provider keys (AI provider registry + universal searchable model picker (OpenRouter, OpenAI-compatible, Ollama) #144).Trust
A stdio MCP server is arbitrary command execution. Registry entries created by the user in Settings are user-authored (like local hooks — always trusted). Anything imported (from a repo file or a shared JSON) must go through explicit confirmation before first launch, mirroring the hooks trust model. Never auto-start an MCP server whose definition arrived via
git pull.Related: #145 (SproutGit's own tools), #143 (roster), #99 (MCP surface).