Feature Request: Pass MCP tool access to Task subagents

Problem

When using the Task tool to spawn subagents, they do not have access to MCP (Model Context Protocol) server tools. MCP connections are established at the session level and not inherited by subagents.

This means specialized agents (like a skylight-calendar-manager agent) cannot use MCP tools even when their purpose is to interact with that specific MCP server.

Current Behavior

1. Main Claude Code session connects to MCP servers (e.g., Skylight calendar)
2. MCP tools are available in the main session
3. When spawning a subagent via Task tool, the agent:

• Can see MCP tools mentioned in system prompts
• Cannot actually invoke MCP tools
• Has access only to standard tools (Bash, Read, Write, Edit, Glob, Grep, etc.)

Desired Behavior

Subagents spawned via the Task tool should inherit MCP tool access from the parent session, allowing them to:

• Use MCP tools relevant to their specialized purpose
• Complete tasks autonomously without returning control to the main session

Use Case

Creating a skylight-calendar-manager agent to batch-create 120+ chores in Skylight. Currently, all MCP calls must be made directly in the main conversation, consuming context and preventing true delegation.

Proposed Solution

Either:

1. Pass MCP tool bindings to subagents automatically
2. Allow specifying which MCP servers a subagent should have access to via a Task parameter (e.g., mcp_servers: ["skylight"])
3. Allow subagents to "request" MCP access from the parent session

Environment

• Claude Code CLI
• CachyOS (Arch Linux)
• MCP Server: @eaglebyte/skylight-mcp