Axiom Docs

Axiom MCP Server is a Model Context Protocol server implementation that enables AI agents to query your data using Axiom Processing Language (APL).

Current capabilities

Supported MCP tools

Axiom MCP Server supports the following MCP tools:

getDatasetSchema: Get dataset schema
getMonitors: List monitoring configurations
getMonitorsHistory: Get monitor execution history
getSavedQueries: Retrieve saved APL queries
listDatasets: List available Axiom datasets
queryApl: Execute APL queries against Axiom datasets

Supported MCP prompts

Axiom MCP Server supports the following MCP prompts:

correlate-events-across-datasets: Find patterns and correlations between events across multiple datasets
data-quality-investigation: Investigate data quality issues including missing data, inconsistencies, and collection problems
detect-anomalies-in-events: Generic anomaly detection using statistical analysis and pattern recognition across any dataset
establish-performance-baseline: Establish performance baselines for a dataset to enable effective monitoring and anomaly detection
explore-unknown-dataset: Exploration of an unknown dataset to understand its structure, content, and potential use cases
monitor-health-analysis: Comprehensive analysis of monitor health, alert patterns, and effectiveness

Axiom plans to support MCP resources in the future. Axiom MCP Server works with all AI agents that support MCP.

Prerequisites

Create an Axiom account.
Create a dataset in Axiom where you send your data.

Setup

If you’re on the Pro, Team, or Enterprise plan:

Add Axiom to the list of remote MCP servers:
- If you’re on the Pro plan, follow the Claude documentation to add Axiom to the list of remote MCP servers using the URL https://mcp.axiom.co/mcp.
- If you’re on the Team or Enterprise plan, ask your organization admin to follow the Claude documentation to add Axiom to the list of remote MCP servers using the URL https://mcp.axiom.co/mcp.
In Claude.ai or Claude Desktop, go to Settings > Connectors.
Find Axiom in the list.
Click Connect.
Authenticate the request in your browser.

If you’re on the Free plan:

Install Claude Desktop.
In Claude Desktop, go to Settings > Developers, and then click Edit Config.

Add the following to claude_desktop_config.json:

claude_desktop_config.json

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

Restart Claude Desktop.
Authenticate the request in your browser.

The setup explained above uses a remote MCP connection and is the recommended approach for most use cases. Alternatively, deploy Axiom MCP Server locally on your machine for more control.

Local setup

With the local setup:

You run Axiom MCP Server yourself.
You authenticate using an API token instead of OAuth 2.0.
You can’t use the MCP prompts mentioned in Current capabilities.

Install

Run the following to install the latest built binary from GitHub:

go install github.com/axiomhq/axiom-mcp@latest

Axiom MCP Server is an open-source project and welcomes your contributions. For more information, see the GitHub repository.

Create API token

Create an API token in Axiom with permissions to update the dataset you have created.

Configure

Configure your AI agent to use the MCP Server in one of the following ways:

Use a config file
Use environment variables

Config file

Create a config file where you specify the authentication and configuration details. For example:
config.txt
```
token API_TOKEN
url https://AXIOM_DOMAIN
query-rate 1
query-burst 1
datasets-rate 1
datasets-burst 1
monitors-rate 1
monitors-burst 1
```
Replace API_TOKEN with the Axiom API token you have generated. For added security, store the API token in an environment variable.Replace AXIOM_DOMAIN with api.axiom.co if your organization uses the US region, and with api.eu.axiom.co if your organization uses the EU region. For more information, see Regions.
Optionally, configure the rate and the burst limits at the query, dataset, and monitor levels. The rate limit is the maximum number of requests that your AI agent can make per second. The burst limit is the maximum number of requests that your AI agent can make in a short period (burst) before the rate limit applies to further requests.
In the settings of your AI agent, reference the binary file of Axiom MCP Server and the config file you have previously created. For example, if you use the Claude desktop app, add axiom to the mcpServers section of the Claude configuration file. The default path is ~/Library/Application Support/Claude/claude_desktop_config.json on MacOS and %APPDATA%\Claude\claude_desktop_config.json on Windows.
claude_desktop_config.json
```
{
  "mcpServers": {
    "axiom": {
      "command": "PATH_AXIOM_MCP_BINARY",
      "args": [
        "--config",
        "PATH_AXIOM_MCP_CONFIG"
      ]
    }
  }
}
```
Replace PATH_AXIOM_MCP_BINARY with the path the binary file of Axiom MCP Server.Replace PATH_AXIOM_MCP_CONFIG with the path the config file you have previously created.

Environment variables

In the settings of your AI agent, use environment variables to specify the authentication details and the binary file of Axiom MCP Server.For example, if you use the Claude desktop app, add axiom to the mcpServers section of the Claude configuration file. The default path is ~/Library/Application Support/Claude/claude_desktop_config.json on MacOS and %APPDATA%\Claude\claude_desktop_config.json on Windows.

claude_desktop_config.json

{
  "mcpServers": {
    "axiom": {
      "command": "PATH_AXIOM_MCP_BINARY",
      "env": {
        "AXIOM_TOKEN": "API_TOKEN",
        "AXIOM_URL": "https://AXIOM_DOMAIN",
        "AXIOM_QUERY_RATE": "1",
        "AXIOM_QUERY_BURST": "1",
        "AXIOM_DATASETS_RATE": "1",
        "AXIOM_DATASETS_BURST": "1",
        "AXIOM_MONITORS_RATE": "1",
        "AXIOM_MONITORS_BURST": "1"
      }
    }
  }
}

Replace PATH_AXIOM_MCP_BINARY with the path the binary file of Axiom MCP Server.Replace API_TOKEN with the Axiom API token you have generated. For added security, store the API token in an environment variable.Replace AXIOM_DOMAIN with api.axiom.co if your organization uses the US region, and with api.eu.axiom.co if your organization uses the EU region. For more information, see Regions.

Optionally, configure the rate and the burst limits at the query, dataset, and monitor levels. The rate limit is the maximum number of requests that your AI agent can make per second. The burst limit is the maximum number of requests that your AI agent can make in a short period (burst) before the rate limit applies to further requests.

Use MCP Server

After setting up the Axiom MCP Server, you can:

Ask your own questions about your event data. For example:
- “List datasets.”
- “Get the data schema for the dataset logs.”
- “Get the most common status codes in the last 30 minutes in the dataset logs.”
Use the prebuilt prompts. For example, in Claude, click + > Add from Axiom to access them.

To answer your questions, your AI client can use the supported MCP tools.

Revoke access

Using the procedure above, you authorized your AI client to access your event data in Axiom. To revoke access:

In Axiom, go to Settings > Profile.
In the Sessions section, find the session where you authorized your AI client, and then click Delete on the right.

If you connected to Axiom MCP Server by adding mcp-remote to claude_desktop_config.json, clear the .mcp-auth folder. This is where Axiom MCP Server stores credential information. On a Mac, the default path is ~/.mcp-auth.

Platform overview

Send data

Console

AI engineering

Miscellaneous

Axiom MCP Server

Current capabilities

Supported MCP tools

Supported MCP prompts

Prerequisites

Setup

Local setup

Install

Create API token

Configure

Config file

Environment variables

Use MCP Server

Revoke access

Platform overview

Send data

Console

AI engineering

Miscellaneous

​Current capabilities

​Supported MCP tools

​Supported MCP prompts

​Prerequisites

​Setup

​Use MCP Server

​Revoke access

Current capabilities

Supported MCP tools

Supported MCP prompts

Prerequisites

Setup

Use MCP Server

Revoke access