manage-mcplisted

# Manage MCP Servers Keep MCP ownership provider-native. Agent Bridge coordinates the provider process; the provider CLI owns its MCP client and configuration. ## Before changing configuration 1. Identify the MCP server's authoritative package/repository/documentation and its required transport: local stdio or remote HTTP/SSE/streamable HTTP. 2. Confirm the installed provider CLI and version. Do not infer support from another provider or from historical qualification. 3. Prefer a pinned MCP package/version on managed or unattended hosts. Do not silently float `latest` when Agent Bridge depends on the contract. 4. Treat a newly requested remote MCP, executable, or credential scope as an external trust boundary. Use only the server/integration the user authorized. ## Provider-native configuration Configure only providers that are installed and natively support the requested MCP. Inspect the installed CLI's current help/documentation before mutating configuration because these surfaces can change between qualified versions. - Claude: use Claude's native `claude mcp` commands or its normal user/project MCP configuration for the intended scope. - Codex: use native `codex mcp` commands / Codex's native MCP entries. - Agy `1.1.19` was qualified with native `agy mcp add/remove/list/enable/disable`; its configuration was observed at `~/.gemini/config/mcp_config.json`. The earlier Agy `1.1.12` no-MCP result is historical, not a current capability rule. - Grok Build `1.0.5` was qu