What problem does it solve? Managing Model Context Protocol servers across projects is error-prone: tokens get committed to repos, configs scatter across IDE files, and servers that "installed fine" silently fail to connect. This Skill routes all MCP management through the APX CLI so scopes, secrets, and merge order stay consistent. ## Core Features & Use Cases - Scoped registration: Add MCP servers to shared (committed), runtime (per-project, chmod 0600, secrets-safe), or global (machine-wide) scopes with correct precedence resolution. - Verification and debugging: Prove a server works with apx mcp tools, inspect spawn/init failures via apx mcp logs, and call tools directly with apx mcp run. - Use Case: You need a GitHub MCP with a personal token for one project. Add it with apx mcp add github --scope runtime --env GITHUB_TOKEN=$TOKEN, then confirm it exposes tools before relying on it. ## Quick Start Ask the agent to list the currently registered MCP servers for your project and add a new one in the appropriate scope.