Axiom MCP Server

What is Axiom MCP Server?

A Zed extension for the official Axiom MCP server, enabling Zed users to interact with Axiom through the Model Context Protocol. It requires an Axiom API token for authentication.

How to use Axiom MCP Server?

Create a config.txt file containing at minimum your Axiom API token (e.g. token xaat-your-token), then add the file path as config_path in your Zed settings.json under the mcp-server-axiom context server settings.

Key features of Axiom MCP Server

• Zed extension for the Axiom MCP server
• Configured via a token in a file on your system
• Uses an Axiom API token for authentication
• Integrates with Zed’s context server system

Use cases of Axiom MCP Server

• —

FAQ from Axiom MCP Server

What is needed to configure Axiom MCP Server?

At minimum, an Axiom API token stored in a config.txt file and the path to that file set in Zed’s settings.json.

Where should the config file be placed?

Anywhere on your system; the full path must be specified in the config_path setting in Zed.

Is an Axiom API token mandatory?

Yes. The configuration file must contain at least token xaat-your-token.

Does Axiom MCP Server run as a separate process?

The README does not specify transport or execution details beyond being a Zed extension for the MCP server.

What runtime dependencies are required?

The README mentions only the Zed editor and an Axiom account with an API token; no other dependencies are listed.