About Axiom MCP Server
A deprecated Zed extension wrapping Axiom's archived MCP server. It required an Axiom API token and a config file; the project recommends the official Axiom remote MCP server instead.
Key features
- 01Zed extension for Axiom MCP
- 02Configuration through a token file
- 03Deprecated and no longer maintained
Use cases
- 01Existing Zed setups using the archived server
- 02Finding the recommended replacement server
MCP support
This Zed extension wrapped Axiom's now-deprecated MCP server. The README directs users to the official remote MCP server at https://mcp.axiom.co.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEAxiom MCP Server
Warning
This extension is deprecated and no longer maintained.
The Axiom MCP server this extension wraps has been deprecated and archived by Axiom. Please use the official Axiom remote MCP server at https://mcp.axiom.co instead.
A Zed extension for the Axiom MCP server.
Configuration
To configure the Axiom MCP server, create a config.txt file somewhere on your system.
At a minimum it should contain your Axiom API token:
token xaat-your-token
Then in your Zed settings.json, add the path to the config.txt file to your settings as the config_path:
"context_servers": {
"mcp-server-axiom": {
"settings": {
"config_path": "/path/to/config.txt"
}
}
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.