Axiom MCP server

Integrates with Axiom's log management platform to query and analyze log data directly within Zed, enabling developers to investigate application logs and troubleshoot issues without leaving their coding environment.
Back to servers
Setup instructions
Provider
Zed Industries
Release date
Mar 21, 2025
Language
Rust
Stats
5 stars

The Axiom MCP Server is a Zed extension that provides integration with Axiom through the Model Context Protocol (MCP). It allows you to connect your Zed editor to Axiom's data platform, enabling efficient data access and manipulation directly from your development environment.

Configuration

Setting Up Config File

To configure the Axiom MCP server, you need to create a config.txt file on your system with your authentication details.

At a minimum, the config file should contain your Axiom API token:

token xaat-your-token

Configuring Zed

After creating your config file, you need to update your Zed settings to point to this configuration:

  1. Open your Zed settings.json file
  2. Add the MCP server configuration with the path to your config file:
"context_servers": {
  "mcp-server-axiom": {
    "settings": {
      "config_path": "/path/to/config.txt"
    }
  }
}

Usage

Once configured, the Axiom MCP server will be available in your Zed editor. You can now use Axiom's features directly within your development workflow.

The server handles the communication between your Zed editor and the Axiom platform, allowing you to:

  • Query your Axiom datasets
  • Analyze data directly from your editor
  • Use Axiom's features without leaving your development environment

For specific Axiom operations and commands, refer to the contextual help available in Zed after completing the configuration.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "mcp-server-axiom" '{"command":"npx","args":["-y","@axiomhq/mcp-server-axiom"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "mcp-server-axiom": {
            "command": "npx",
            "args": [
                "-y",
                "@axiomhq/mcp-server-axiom"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "mcp-server-axiom": {
            "command": "npx",
            "args": [
                "-y",
                "@axiomhq/mcp-server-axiom"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later