Let user-level MCP servers reach every provider's agents, not only Claude and Codex

AgentsRoom injects its own MCP servers (AgentsRoom-MCP, Test-Runner, QA-Tester) into all 14 providers at launch, in each CLI's native config format. That works well. But a user's OWN MCP servers reach agents only through "Use my personal CLI configuration" (inheritUserCliConfig), which:

• covers Claude and Codex only (the two providers whose config root AgentsRoom relocates);
• is all-or-nothing: it loads the entire personal layer (every user MCP server, hooks, plugins, skills) into every managed account. For a Codex config with 28 servers that is not usable as a way to expose two of them.

For Grok, Kimi, Antigravity and the other providers there is no path at all: AgentsRoom writes only its own servers into the project-level config it generates. The managed Codex home is regenerated on every spawn, so nothing added there survives either.

Observed: a remote MCP server registered in ~/.claude.json is available to Claude agents; the same server registered in ~/.codex/config.toml is invisible to Codex agents; Grok, Kimi and Antigravity agents cannot be given it through AgentsRoom by any setting.

Steps: register any remote MCP server in the user-level config of Codex, Grok, Kimi or Antigravity; launch an agent of that provider from AgentsRoom; list its MCP servers. Only the AgentsRoom-* servers appear (Codex, Kimi), or the server appears only because the CLI happens to read the user's own home directly (Grok), which AgentsRoom does not control or document.

AgentsRoom diagnostics

• App version: 1.173.0
• OS: darwin 25.6.0 (arm64)
• Agent CLI: claude
• App language: system

Problem to solve

User-declared MCP servers reach only Claude/Codex agents, and only via the all-or-nothing inheritUserCliConfig switch. Grok, Kimi, Antigravity and the other providers have no supported path; the managed Codex home is regenerated per spawn.

Proposed behavior

A way to declare additional MCP servers that AgentsRoom writes alongside its own into every provider's generated config, per project or per provider, with {{secret:NAME}} support for auth headers, the same way Environment variables already work at those scopes.

Who benefits

Anyone running a private remote MCP server (e.g. a Cloudflare Worker) they want every agent in a project to use regardless of provider, with the bearer token kept in the AgentsRoom secret store.

Acceptance criteria

One declaration; every agent of every provider in the project sees the server with its credential injected; no hand-editing of generated profiles.