A community-driven registry for Claude, Cursor, Windsurf, Cline & more. Not affiliated with Anthropic.
Are you the author? Sign in to claim
苹果 MCP 工具 ✅
mcpx is a command line tool that turns registered MCP servers into an agent-friendly command surface.
It keeps MCP server registrations in a global user registry, discovers tool schemas, handles OAuth where possible, and exposes each MCP server as a root command:
mcpx posthog projects-get
mcpx sentry search-issues --input '{"query":"is:unresolved"}'
mcpx is designed for agents. The command surface is intentionally schema-first,
stable, and explicit: tool calls pass input through --input, while mcpx's own
control commands live under the @ namespace.
Install the latest release:
curl -fsSL https://raw.githubusercontent.com/AIGC-Hackers/mcpx/main/install.sh | bash
By default, the installer downloads the executable JS bundle from GitHub Releases
and installs it to ~/.local/bin/mcpx.
Set MCPX_INSTALL_DIR to choose another install directory.
Register MCP servers globally:
mcpx @add --name posthog --url https://mcp.posthog.com/mcp
mcpx @add --name sentry --url https://mcp.sentry.dev/mcp
mcpx @add --name cf-docs --url https://docs.mcp.cloudflare.com/mcp
mcpx @add --name cf-bindings --url https://bindings.mcp.cloudflare.com/mcp
mcpx @add --name cf-observability --url https://observability.mcp.cloudflare.com/mcp
mcpx @add --name browser --url http://127.0.0.1:9000/mcp
browser-os is an agent-native browser built on Chrome. It exposes a local MCP server that lets agents control the browser directly — navigating pages, extracting content, and interacting with web UIs.
mcpx stores server configuration in:
~/.agents/mcpx/servers.json
OAuth tokens and client secrets are stored separately in the global token cache:
~/.agents/mcpx/tokens.json
Project directories do not need MCP config files. A project should decide which global servers are relevant by using schema selectors or a generated skill.
Call tools through the server command:
mcpx <server> <tool> --input '<json-or-json5>'
Examples:
mcpx posthog projects-get --input '{}'
mcpx sentry whoami --input '{}'
For complex payloads, use @- with a heredoc to keep the input readable:
mcpx cf-graphql graphql_query --input @- <<'JSON'
{
"query": "query GetWorkerAnalytics($accountTag: String!, $scriptName: String!, $since: Time!, $until: Time!) { viewer { accounts(filter: {accountTag: $accountTag}) { workersInvocationsAdaptive(limit: 1000, filter: {scriptName: $scriptName, datetime_geq: $since, datetime_leq: $until}, orderBy: [datetimeHour_ASC]) { dimensions { datetimeHour scriptName status } sum { requests subrequests errors duration } quantiles { cpuTimeP50 cpuTimeP99 } } } } }",
"operationName": "GetWorkerAnalytics",
"variables": {
"accountTag": "abc123def456",
"scriptName": "my-worker",
"since": "2026-04-20T00:00:00Z",
"until": "2026-04-27T00:00:00Z"
}
}
JSON
--input is the primary input path. It accepts inline JSON/JSON5, @file, and
@- stdin inputs.
Print the command schema for agents:
mcpx --schema
Focus on one server:
mcpx --schema=.posthog
Focus on a set of servers:
mcpx --schema='.{posthog,sentry}'
Focus on an internal mcpx command:
mcpx --schema='.["@add"]'
mcpx caches discovered tool schemas in the global registry. Cached schemas older than one day are refreshed opportunistically in a single background worker when mcpx starts, so normal commands do not block on schema discovery. Servers that have not discovered any tools yet are still retried synchronously during startup.
mcpx control commands use the @ namespace so they do not collide with server
names:
mcpx @add --name <server> --url <mcp-url>
mcpx @add --name <server> --transport stdio --command <command> --arg <arg>
mcpx @remove --name <server>
mcpx @refresh
mcpx @daemon status
mcpx @daemon stop
mcpx @daemon server
mcpx @skill
Server names cannot start with @.
HTTP is the default transport. Stdio servers are local process registrations;
pass each process argument with --arg, or use --input when you need structured
args / env:
mcpx @add --input '{
"name": "open-design",
"transport": "stdio",
"command": "node",
"args": ["/path/to/open-design/apps/daemon/dist/cli.js", "mcp"],
"env": { "OPEN_DESIGN_TOKEN": "..." }
}'
@refresh checks every registered MCP server, repairs OAuth state first,
refreshes cached tool schemas after auth is ready, and reports servers that
still require re-authentication. It may open a browser for interactive OAuth.
Stdio servers are called through mcpxd, a user-local daemon that reuses stdio
MCP sessions across CLI invocations. mcpxd starts on demand, keeps idle stdio
servers warm, and can be inspected or stopped with mcpx @daemon status and
mcpx @daemon stop. The daemon process is started through the explicit
mcpx @daemon server subcommand. HTTP servers continue to use the direct client path.
When @add detects OAuth, mcpx tries to complete authentication immediately.
For OAuth servers that support dynamic client registration, mcpx registers a
client automatically.
For OAuth servers that do not support dynamic client registration, such as
Slack, mcpx prompts for a manual client_id and client_secret. These providers
usually require a preconfigured redirect URL. mcpx uses:
http://127.0.0.1:65245/callback
Add and save that exact Redirect URL in the provider app settings before continuing the prompt.
When an OAuth token is close to expiry, mcpx refreshes it before calling the MCP tool and then continues the original command.
Tool calls use a 5 minute request timeout by default. Set
MCPX_TOOL_CALL_TIMEOUT_MS when a remote MCP server legitimately needs longer.
mcpx optimizes output for humans and agents by default:
file saved <path>Use --raw to preserve raw server text output:
mcpx posthog projects-get --raw
Generate a project-local skill that tells agents which global MCP servers to use:
mcpx @skill --servers posthog,sentry
This writes:
.agents/skills/mcpx/SKILL.md
The generated skill instructs agents to discover tools with focused schema selectors and call MCP tools through mcpx.
For temporary agent guidance without writing .agents/skills, print a one-server
skill to stdout:
mcpx @skill --show slack
General mcpx skill definition lives at skills/mcpx/SKILL.md.
MIT
A Jetbrains IDE IntelliJ plugin aimed to provide coding agents the ability to leverage intelliJ's indexing of the codeba
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots