Feature Request: MCP Connection Inheritance for Sub-Agents

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When spawning sub-agents (teammates) via the Agent tool, MCP server connections established in the parent session are not available to the child agents, even when the agent type definition explicitly lists MCP tools in its capabilities.

Proposed Solution

One of the following approaches:

Option A: Connection Handle Passthrough

When spawning a sub-agent, pass the parent's MCP server connection handles to the child process. The child reuses the existing connections.

Option B: Independent MCP Connection per Agent

Each sub-agent establishes its own MCP connections based on the session's MCP configuration. This provides better isolation but may have resource implications.

Option C: Shared MCP Proxy

Introduce a session-level MCP proxy that multiplexes requests from all agents (parent + children) over shared server connections.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

In a multi-agent team workflow (using TeamCreate + Agent), different roles need different tools:

• qa-engineer needs chrome-devtools MCP to perform visual interaction testing (navigate pages, take screenshots, click elements, verify UI behavior)
• engineer agents may need MCP tools for database access, deployment, or other integrations

Currently, the only workaround is for the parent agent (team-lead) to manually execute MCP operations and relay results to sub-agents, which breaks the separation of concerns and adds unnecessary coordination overhead.

Additional Context

_No response_