per_agent_mcp
Whether agents can have their own MCP server configuration, scoping which external tools each agent can access.
Type: bool Content type: agents
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| claude-code | ✓ | mcpServers frontmatter field: list of server names referencing already-configured workspace servers or inline server definitions; ignored for plugin subagents |
| copilot-cli | ✓ | mcp-servers inline config in frontmatter; available for cloud agent only; workspace MCP config shared by default |
| gemini-cli | ✓ | mcpServers object in frontmatter; declares inline MCP server configurations scoped to this subagent. Each entry follows the same shape as the global mcpServers config and is isolated to the subagent's invocation. |
| kiro | ✓ | inline mcpServers map per agent config; includeMcpJson boolean controls whether workspace .kiro/settings/mcp.json is merged into agent's server set |
| amp | ✗ | not documented |
| cline | ✗ | not documented |
| codex | ✗ | MCP configuration is workspace-wide; no per-role MCP scoping mechanism |
| crush | ✗ | not documented |
| cursor | ✗ | Cursor custom agents do not document a per-agent mcpServers field; they inherit the workspace MCP configuration. |
| factory-droid | ✗ | no per-droid MCP configuration documented; MCP is workspace-wide; droids can use MCP tools via the mcp tool category |
| opencode | ✗ | OpenCode agent frontmatter does not document a per-agent mcpServers field; agents inherit the workspace MCP configuration. Per-agent tool access to MCP tools is controlled via the permission map (e.g., mymcp_*: deny) rather than a separate MCP config. |
| pi | ✗ | not documented |
| roo-code | ✗ | Custom modes do not declare their own MCP server lists — MCP configuration is global per the .roo/mcp.json and global MCP settings |
| windsurf | ✗ | not documented |
| zed | ✗ | not documented |