mcp -axiom

This MCP server integrates the Axiom MCP server with Zed as a dedicated extension. It relies on a configuration file (config.txt) containing your Axiom API token and exposes a simple way for Zed users to connect to the Axiom MCP backend. To use it, first generate or obtain a config.txt that includes your Axiom API token (for example: 'token xaat-your-token'). Then point the Zed extension to that file by editing the Zed settings.json and adding the path under config_path for the mcp-server-axiom server. Once configured, the MCP server will authenticate with Axiom and provide the MCP protocol endpoints needed by Zed to process and forward events to Axiom.

Key capabilities include: reading the Axiom token from config.txt, authenticating with the Axiom MCP service, and exposing the MCP endpoints that Zed expects so you can stream events from Zed to Axiom through this server. Ensure your environment has network access to Axiom's APIs and that the config_path points to a readable text file containing the token line as shown in the example.

Prerequisites:

• Node.js (recommended: current LTS) and npm installed on your system
• Access to the internet to fetch the MCP server package

Installation steps:

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v

2. Use npx to run the MCP server package (no global install required): npx -y mcp-server-axiom

3. Create and configure the config.txt file with your Axiom API token, e.g.: token xaat-your-token

4. In your Zed settings.json, specify the path to the config.txt file for the mcp-server-axiom server: { "context_servers": { "mcp-server-axiom": { "settings": { "config_path": "/path/to/config.txt" } } } }

5. Start or reload Zed and verify that the mcp-server-axiom server connects and starts streaming events to Axiom.

Notes and tips:

• The server expects a config.txt containing a line starting with 'token' followed by your API token. Example: 'token xaat-your-token'.
• Ensure the file path specified in config_path is accessible by the process running Zed.
• If you encounter authentication errors, double-check that the token is current and has the necessary permissions in Axiom.
• Network access to Axiom's MCP endpoints is required; verify firewall and proxy settings if applicable.
• When updating the token, restart the MCP server or trigger a reload to pick up changes.
• This configuration uses npx to fetch and run the mcp-server-axiom package; if you prefer a persistent installation, you can explore using a local installation via npm install -g mcp-server-axiom and adjust the command accordingly.