Axiom MCP Server (Official Remote)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "axiom-mcp-server-official-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.axiom.co/mcp"
      ]
    }
  }
}

Before you start

• An Axiom account with at least one dataset
• For the hosted remote server: an MCP client that supports OAuth (you sign in through the browser, no token to copy)
• For the self-hosted Go binary: an Axiom API token (format xaat-...), created in the Axiom console under Settings → API tokens, set via AXIOM_TOKEN
• Go (only if installing the legacy binary via `go install github.com/axiomhq/axiom-mcp@latest`)

About Axiom MCP Server (Official Remote)

Tools & capabilities (6)

When to use it

• Use it when you want to investigate logs or traces by asking questions in natural language and letting the agent write APL
• Use it when you need to discover what datasets and fields exist before querying
• Use it when you want to reuse saved queries during an incident investigation
• Use it when you want to check monitor status and history while debugging an alert
• Use it when you want to pull event/log data into an AI workflow for summarization or root-cause analysis

Quick setup

1. 1Point your MCP client at the hosted remote server `https://mcp.axiom.co` (recommended)
2. 2Complete the OAuth sign-in flow in your browser when the client connects
3. 3Or, for self-hosting, install the Go binary and set AXIOM_TOKEN (and AXIOM_URL for non-default regions) before launching it over stdio
4. 4Restart your MCP client to load the server
5. 5Verify by asking the agent to list your datasets, then run a simple APL query

Axiom MCP Server (Official Remote) FAQ