Developers · CLI
Your MCP instance, from the terminal.
amcp calls MCP tools and drives the full management API — by hand, in scripts, or from a connected agent. One npm install, browser login, and everything the dashboard does is a command away.
Open source (AGPL-3.0) · works on Cloud and self-hosted · Node 22+
$ npm i -g @anythingmcp/cliadded 1 package · amcp ready$ amcp login --browser→ approve in cloud.anythingmcp.com✓ signed in (management · scope: admin)$ amcp api GET /api/mcp-servers --json[ { "id": "srv_ops", "name": "Ops", "tools": 42 } ]
Two jobs, one tool
The same binary speaks MCP and the management API, with the credential you grant it.
Call MCP tools
Discover tools, read their schema, and run them from your shell — the same tools your AI clients use.
Manage the instance
Connectors, MCP servers, users, roles, SSO, memory, skills and settings — every /api/* route, with a management-scoped key.
Everything in a few commands
A management key carries the owner's identity and role — it never grants privilege, and read-only keys can only read.
Log in
Browser login mints a key over a one-shot loopback — it never touches a URL, log or shell history.
$ amcp login --browser$ amcp login --browser --scope admin
Add tools from any API
Turn an OpenAPI, WSDL, GraphQL, Postman, cURL or HAR source into MCP tools — or pull them from another MCP server.
# from OpenAPI · WSDL · GraphQL · Postman · cURL$ amcp api POST /api/connectors/$ID/import-spec --data @spec.json# or pull them from another MCP server$ amcp api POST /api/connectors/$ID/discover-tools
Code mode & servers
Switch a server to code mode so an agent writes and runs code against your tools in a sandbox — and spin up new MCP servers.
# let an agent write & run code against your tools$ amcp api PUT /api/mcp-servers/$ID --data '{"codeMode":"tools"}'$ amcp api POST /api/mcp-servers --data '{"name":"ops"}'
Everything from the terminal
Discover the whole API, call any tool, and add shell completion.
$ amcp api --list # discover 200+ operations$ amcp tools call YOUR_TOOL --args @args.json$ amcp completion zsh
Built for agents, too
The same management API is exactly what a connected agent needs to onboard and run a workspace end to end — add a connector, create a server, assign roles, wire SSO — safely, within the scope you grant it. Agents default to read-only, and every call is rate-limited and audited.
Secure by default
The API key is never accepted as a command argument and never printed in status output.
Keys are stored with file mode 0600; HTTPS is required except on loopback for local dev.
Redirects are refused, so a key can't follow a request to another origin.
A per-key rate limit refuses a runaway client instead of hammering your instance.
Get it
Install globally, then log in to your Cloud or self-hosted instance.
Install the CLI
Two minutes to your first call. No AnythingMCP yet? Start free on Cloud, or self-host it.