About Axis MCP

Axis MCP is a curated registry of Model Context Protocol (MCP) servers, with ready-to-adapt configuration for the AI coding clients people actually use.

What Axis MCP is

MCP lets AI agents call external tools: databases, cloud platforms, developer services and productivity apps. Each client wants its configuration in a different format. Axis MCP keeps a short, hand-maintained list of MCP servers and shows each one with its transport, the setup it needs, example tools, a link to its upstream documentation, and configuration examples for Claude Code, Cursor, Codex CLI, Antigravity / Gemini CLI, OpenCode and VS Code Copilot.

The same catalog is available to programs: as JSON at /api/v1/servers, as plain text at /docs/client-configurations.txt, and as a read-only MCP server at https://axismcp.dev/mcp.

Who runs it

Axis MCP is run by DeadStock Systems and maintained by William. Questions, corrections and sponsorship enquiries go to [email protected]; see the contact page.

How servers are chosen and checked

Listings are curated, not scraped. Every entry lives in a single reviewed catalog file, and an automated validator rejects it before publication unless:

Anyone can propose a server with the Submit a server button on the home page. A proposal goes into a private review queue; nothing is published automatically. Changes to the live catalog go through a reviewed workflow that backs up the current data, pins the exact change and needs a manual confirmation before anything is written.

What a listing does not mean: the configuration examples are not tested connections, tool names are upstream examples, and inclusion is not a security or compatibility endorsement. Paid placement, if any, is labelled separately and does not change ordering. Always read the upstream documentation before giving a server access to your accounts or data.

How often it is updated

GitHub star counts shown for listed servers are refreshed automatically once a week (Sundays, 04:00 UTC). Server entries, descriptions and configuration examples change when a reviewed update is published, rather than on a fixed schedule. The registry home page and the JSON API always read the current catalog.