home / mcp / axiom mcp server

Axiom MCP Server

Axiom Model Context Protocol Server

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "axiomhq-mcp-server-axiom": {
      "url": "https://api.axiom.co",
      "headers": {
        "AXIOM_URL": "https://api.axiom.co",
        "AXIOM_TOKEN": "xaat-your-api-token",
        "AXIOM_QUERY_RATE": "1",
        "AXIOM_QUERY_BURST": "1",
        "AXIOM_DATASETS_RATE": "1",
        "AXIOM_MONITORS_RATE": "1",
        "AXIOM_DATASETS_BURST": "1",
        "AXIOM_MONITORS_BURST": "1"
      }
    }
  }
}

You can run an MCP server for Axiom that lets AI agents query your Axiom data using the Axiom Processing Language (APL). This server exposes both a remote HTTP MCP endpoint and a local development/Runtime MCP channel so your client applications can connect in the way that fits your deployment needs.

How to use

You connect to the Axiom MCP Server from your MCP-compatible client by using either the remote HTTP endpoint or the local stdio-based runtime. The HTTP method points to the Axiom API, while the stdio method runs a local MCP process and communicates via standard I/O. You can enable and tune two aspects: the remote API access and the local runtime for development or internal workflows. The available tools let you query APL, inspect datasets, retrieve saved queries, and monitor history.

How to install

# HTTP-based MCP server configuration (remote)
{
  "type": "http",
  "name": "axiom",
  "url": "https://api.axiom.co",
  "args": []
}
```.

# STDIO-based MCP server configuration (local runtime)
{
  "type": "stdio",
  "name": "axiom",
  "command": "/path/to/your/axiom-mcp-binary",
  "args": ["--config", "/path/to/your/config.txt"],
  "env": {
    "AXIOM_TOKEN": "xaat-your-api-token",
    "AXIOM_URL": "https://api.axiom.co"
  }
}

Additional configuration and usage notes

Configure API tokens and rates to control how often queries are executed and how many requests can be burst. The HTTP configuration uses a token and the remote URL, while the local STDIO configuration runs a binary with a JSON-style config and environment variables to supply credentials.

Configuration and environment variables

The following environment variables are commonly used to configure the MCP server when running in STDIO mode. You can set these in your shell or export them in a runtime environment.

Tools and capabilities

The MCP server exposes six tools for interacting with Axiom data and configurations. Each tool is accessed via the MCP interface and targets specific operations on datasets and monitors.

Troubleshooting

If you cannot connect to the remote endpoint, verify that the URL is reachable and that your token is valid. If you run the local runtime and see authentication errors, confirm that AXIOM_TOKEN and AXIOM_URL are correctly set or provided in the config file.

Available tools

queryApl

Execute APL queries against Axiom datasets to retrieve results based on your query.

listDatasets

List available Axiom datasets that you can query or inspect.

getDatasetSchema

Retrieve the schema for a specified dataset to understand its fields and types.

getSavedQueries

Retrieve saved or starred APL queries for quick reuse.

getMonitors

List monitoring configurations that are set to observe data changes or thresholds.

getMonitorsHistory

Get the execution history of monitors to review past runs and outcomes.