apx-mcp

Registers, scopes, and debugs MCP servers through the APX CLI.

6|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/agentprojectcontext/apx --skill apx-mcp-agentprojectcontext
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apx-mcp
Source: https://github.com/agentprojectcontext/apx/tree/main/skills/apx-mcp
Command: npx skills add https://github.com/agentprojectcontext/apx --skill apx-mcp-agentprojectcontext

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about apx-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an MCP server to an APX project?▼

Run apx mcp add with a name and either --command for a local stdio process or --url for a remote HTTP endpoint. Choose the scope with --scope: shared for committed team config, runtime for per-project secrets, or global for machine-wide servers.

Where should I store MCP tokens and API keys in APX?▼

Tokens belong in the runtime scope, stored in ~/.apx/projects/<id>/mcps.json with chmod 0600 and never committed. Never pass secrets to the shared scope, since that file is committed to the repository.

Why does my MCP server show no tools after adding it?▼

apx mcp add only writes JSON and never contacts the server, so a successful add does not mean a working connection. Run apx mcp tools <name> to verify, and apx mcp logs <name> to see the spawn/init log and stderr tail.

What happens when the same MCP name exists in multiple scopes?▼

Runtime scope wins over shared, and shared wins over global; lower-priority entries stay invisible. Conflicts surface when you run apx mcp check for the project.

Can APX remove MCP servers configured in Cursor or Claude?▼

No. APX reads IDE configs like ~/.cursor/mcps.json as advisory sources but never writes to them. Edit those IDE configuration files directly to remove or change them.