Axiom MCP Server

Query and analyze your Axiom logs, traces, and all other event data in natural language

Remote serverstreamable-httpGo

What is the Axiom MCP server?

Axiom mcp server connects Axiom to AI assistants that speak the Model Context Protocol. Query and analyze your Axiom logs, traces, and all other event data in natural language.

What Axiom does

Works with Claude desktop app. Implements six MCP tools:

A Model Context Protocol server implementation for Axiom that enables AI agents to query your data using Axiom Processing Language (APL).

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • Releases — Download the latest built binary from the releases page
  • Source — The Source tool exposed by this server

Installing the axiom mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 8 environment variables: AXIOM_TOKEN, AXIOM_URL, AXIOM_QUERY_RATE, AXIOM_QUERY_BURST, AXIOM_DATASETS_RATE, AXIOM_DATASETS_BURST, AXIOM_MONITORS_RATE, AXIOM_MONITORS_BURST. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. Axiom sits in that group, and the shape of its toolset — Releases, Source — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the axiom mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
ReleasesDownload the latest built binary from the [releases page](https://github.com/axiomhq/axiom-mcp/releases).
SourceThe Source tool exposed by this server.

How to install the Axiom MCP server

```json
{
  "mcpServers": {
    "axiom": {
      "command": "/path/to/your/axiom-mcp-binary",
      "args" : ["--config", "/path/to/your/config.txt"],
      "env": { // Alternatively, you can set the environment variables here
        "AXIOM_TOKEN": "xaat-your-api-token",
        "AXIOM_URL": "https://api.axiom.co"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AXIOM_TOKENCredential the server authenticates with.Yes
AXIOM_URLEndpoint or connection string the server talks to.Yes
AXIOM_QUERY_RATEConfiguration value read at startup.Optional
AXIOM_QUERY_BURSTConfiguration value read at startup.Optional
AXIOM_DATASETS_RATEConfiguration value read at startup.Optional
AXIOM_DATASETS_BURSTConfiguration value read at startup.Optional
AXIOM_MONITORS_RATEConfiguration value read at startup.Optional
AXIOM_MONITORS_BURSTConfiguration value read at startup.Optional

Example prompts to try

  • Use Axiom to Releases.
  • Use Axiom to Source.

Frequently asked questions

It connects Axiom to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Releases, Source) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Axiom directly.