What problem does it solve? Global MCP server configurations apply to every project, which forces teams to either overload the global tool list or manually edit per-project config files. This Skill opts a single repository into extra MCP servers (ast, browser, context7, context, akatsuki) without touching the global set. ## Core Features & Use Cases - Project-scoped activation: Runs enable-mcp <server> <project-root> to symlink the shared library into .agents/plugins/ and merge a mcpServers entry into .pi/mcp.json. - Safe merge and removal: The script merges and unmerges config entries without clobbering the global entry's precedence, and supports disable for clean rollback. - Verification and documentation: Provides enable-mcp status checks and instructs adding an MCP section to the project's AGENTS.md so the choice is discoverable. - Use Case: A developer needs AST blast-radius analysis only in one repository, so they enable the ast server for that project while keeping the global tool list minimal. ## Quick Start Ask the agent to enable the ast MCP server for the current project using the enable-mcp command.