[BUG] Agents Don't Inherit MCP Tool Access Despite Connected MCP Servers

Claude Code Bug Report: Agent MCP Tool Access Inheritance Issue

Summary

Agents launched via the Task tool do not inherit access to MCP (Model Context Protocol) tools, despite MCP servers being properly installed, connected, and accessible to the main Claude instance.

Environment

• Claude Code Version: Latest (as of 2025-01-08)
• Platform: Linux 6.15.8-zen1-1-zen
• Project Path: /home/persist/repos/work/vazio/gateway-coin
• Date Reported: 2025-01-08

Expected Behavior

According to the Task tool description, specialized agents should have access to specific MCP tools:

• Project Manager: Should have access to mcp__pdl__*, mcp__nabu__*, mcp__telos__*, mcp__worktree__*
• Engineering Manager: Should have access to mcp__pdl__*, mcp__nabu__*, mcp__telos__*, mcp__serena__*, mcp__context7__*, mcp__worktree__*, mcp__shamash__*
• Software Engineer: Should have access to mcp__pdl__*, mcp__nabu__*, mcp__telos__*, mcp__serena__*, mcp__context7__*, mcp__worktree__*

Actual Behavior

All agents launched via Task tool report they only have access to basic file operations:

• ✅ Read, Write, Edit, MultiEdit
• ✅ Bash, Glob, Grep
• ❌ NO access to any MCP tools (mcp__pdl__*, mcp__nabu__*, mcp__telos__*, etc.)

Evidence

MCP Servers Are Properly Installed and Connected

$ claude mcp list
Checking MCP server health...

playwright: npx @playwright/mcp@latest - ✓ Connected
context7: https://mcp.context7.com/mcp (HTTP) - ✓ Connected
nabu: node /home/persist/repos/lib/mcp_nabu/dist/index.js - ✓ Connected
telos: uvx --from /home/persist/repos/lib/mcp_telos telos - ✓ Connected
pdl: /usr/bin/node /home/persist/repos/lib/mcp_pdl/dist/server.js - ✓ Connected
shamash: node /home/persist/repos/lib/mcp_shamash/dist/index.js - ✓ Connected
worktree: node /home/persist/repos/lib/mcp-worktree/server.js - ✓ Connected
scribe: /home/persist/repos/lib/mcp_scribe/dist/index.js - ✓ Connected
kr8: node /home/persist/repos/lib/mcp_kr8/mcp-server/dist/index.js - ✓ Connected

Main Claude Instance Has Full MCP Access

• ✅ Can use mcp__pdl__get_status
• ✅ Can use mcp__nabu__active_ports
• ✅ Can use mcp__telos__telos_store
• ✅ Can use all other MCP functions

Agent Test Results

Project Manager Agent Test:

❌ NO PDL Functions Available - I do not have access to mcp__pdl__* functions
❌ NO Nabu Functions Available - I do not have access to mcp__nabu__* functions  
❌ NO Telos Memory Functions Available - I do not have access to mcp__telos__* functions
❌ NO Other MCP Tools Available - Context7, Serena, Worktree, Playwright, Shamash not accessible

✅ Basic file operations (Read, Write, Edit, MultiEdit)
✅ Bash command execution  
✅ File searching (Glob, Grep)

Engineering Manager Agent Test:

❌ NO PDL Functions Available - I do not have access to mcp__pdl__* functions
❌ NO Nabu Functions Available - I do not have access to mcp__nabu__* functions  
❌ NO Telos Memory Functions Available - I do not have access to mcp__telos__* functions
❌ NO Other MCP Tools Available - Context7, Serena, Worktree, Playwright, Shamash not accessible

Reproduction Steps

1. Install and configure MCP servers (PDL, Nabu, Telos, etc.)
2. Verify MCP servers are connected with claude mcp list
3. Verify main Claude instance can access MCP functions
4. Use Task tool to launch any specialized agent (Project Manager, Engineering Manager, etc.)
5. Ask agent to test access to MCP functions they should have according to their description
6. Observe that agents report no MCP access

Impact

This issue breaks the entire agent delegation workflow described in project documentation:

• Project Manager cannot coordinate PDL phases
• Agents cannot communicate via Nabu
• No memory persistence via Telos
• No feature branch management via Worktree
• Forces workarounds that bypass the intended agent architecture

Configuration Details

Critical Configuration Information

• MCP Servers: Installed at USER LEVEL (scope: user config, available in all projects)
• Agents: NOT installed globally - launched via Task tool on-demand
• Project Scope: Local project in /home/persist/repos/work/vazio/gateway-coin

PDL Server Config

pdl:
  Scope: User config (available in all your projects)
  Status: ✓ Connected
  Type: stdio
  Command: /usr/bin/node
  Args: /home/persist/repos/lib/mcp_pdl/dist/server.js

Nabu Server Config

nabu:
  Scope: User config (available in all your projects)
  Status: ✓ Connected
  Type: stdio
  Command: node
  Args: /home/persist/repos/lib/mcp_nabu/dist/index.js

Scope Mismatch Theory

Potential Issue: MCP servers are installed at USER scope, but agents launched via Task tool may not be inheriting user-scoped MCP access. This could be a scope inheritance problem where:

• Main Claude instance ✅ inherits user-scoped MCP servers
• Task-launched agents ❌ don't inherit user-scoped MCP servers

Workaround

Currently using main Claude instance to handle MCP coordination directly instead of delegating to specialized agents, which defeats the purpose of the agent system.

Request

Please investigate why agents launched via Task tool don't inherit MCP server access when:

1. MCP servers are properly configured and connected at USER scope
2. Main Claude instance has full access to user-scoped MCP servers
3. Agent descriptions explicitly state they should have MCP access
4. This appears to be a scope inheritance issue where user-scoped MCP servers aren't passed to Task-launched agents
5. Key Question: Do Task-launched agents inherit user-scoped MCP server access, or do they need different configuration?

Contact

Please respond via the Claude Code interface or GitHub issues if this should be filed elsewhere.