mcpx

# mcpx `mcpx` turns registered MCP servers into an agent-friendly command surface. Use it when a task needs MCP-backed services such as PostHog, Sentry, Cloudflare, or another server registered in the user's global mcpx registry. ## Execution Rules - Run `mcpx` directly. - Start with the server inventory instead of dumping every registered schema. - Call MCP tools as `mcpx <server> <tool> --input <json>`. - Pass all tool arguments through `--input`; do not invent flags for MCP tool fields. - Use focused schema selectors before calling tools on large MCP surfaces. - Do not hand-edit `~/.agents/mcpx/servers.json` or token cache files unless the user explicitly asks for registry surgery. - Treat MCP server registration and OAuth setup as human-owned configuration. If a required server is missing or unauthenticated, stop and ask the user to configure it. ## First Move: Discover The Surface At the start of an MCP task, run bare `mcpx` to list configured servers: ```bash mcpx ``` Choose the likely server from the user's request, then inspect only that server's schema: ```bash mcpx --schema=.sentry mcpx --schema=.posthog ``` After that, narrow to the specific tool or a short candidate list: ```bash mcpx --schema=.posthog.projects-get mcpx --schema='.posthog.{projects-get,alerts-list,alert-create}' ``` Avoid `mcpx --schema` unless the user explicitly asks for the complete command surface. On a real registry it may expand every server schema and waste the agent context. ##...