What problem does it solve?
This Skill solves the confusion around how to discover, name, and grant Claude Code agents access to MCP (Model Context Protocol) tools—especially when using custom sub-agents that do not automatically inherit MCP tool access.
Core Features & Use Cases
- MCP tool naming convention: Establishes the exact tool prefix format based on MCP server names so you can reference tools correctly.
- Sub-agent access configuration: Provides the practical workaround for explicitly listing MCP tool names in a sub-agent’s allowed_tools definition.
- Tool discovery workflow: Shows multiple ways to list available MCP servers and derive tool names for the specific environment you are running.
- Security guardrails: Highlights the risk of destructive actions (e.g., email send/delete) and encourages granting only the tools a sub-agent needs.
Use Case: You have an MCP server configured for email access and want a custom sub-agent to search and fetch emails for a specific task, while ensuring it cannot use unrelated tools.
Quick Start
When your agent needs MCP access, explicitly list the MCP tool names (using the correct mcp__<server>__<tool> naming) under the sub-agent’s allowed_tools.