Axiom MCP Server

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

For guidance on when to use Axiom MCP Server and Axiom Skills, see AI agents.

For the full list of tools and prompts with example queries, see MCP tools reference.

If your agent doesn’t have an Axiom organization to work in yet, it can provision a temporary one itself and hand you a claim link later. For more information, see Agent-created organizations.

Current capabilities

Tools and prompts

Axiom MCP Server works with AI agents that support MCP. It exposes tools for querying data, exploring datasets and metrics, and managing dashboards, monitors, and notifiers, plus prebuilt prompts for common investigations. For the full list with example queries, see MCP tools reference.

The Axiom-hosted MCP Server is located in the US. When you query your data using a remote MCP connection, query results are routed through US infrastructure.

Prerequisites

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

Setup

Remote MCP URL: https://mcp.axiom.co/mcp

Remote MCP with OAuth is the recommended setup for most use cases.

Install with add-mcp

Use the add-mcp CLI to add Axiom MCP Server to your coding agents:

npx -y add-mcp https://mcp.axiom.co/mcp -g

Authenticate in your browser when the agent prompts you.

Optional flags:

• Omit -g to install for the current project only.
• Add -y to skip confirmation prompts.
• Target specific agents with -a, for example -a cursor -a claude-code.

Quick setup

Choose your client to get its fastest setup path, or copy a setup prompt for your AI agent.

claude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp

Header-based authentication

If your AI agent doesn’t support browser-based OAuth (for example, Agent Builder from OpenAI), authenticate with headers:

1. Create a personal access token.

2. Determine organization ID.

3. Configure your AI agent to use https://mcp.axiom.co/mcp.

4. Send these headers with each request:

   • Authorization: Bearer PERSONAL_ACCESS_TOKEN
   • x-axiom-org-id: ORGANIZATION_ID

   If your agent only supports the Authorization header, pass the organization ID as a URL parameter: https://mcp.axiom.co/mcp?org-id=ORGANIZATION_ID

Token hygiene

The remote MCP Server uses OAuth for authentication which handles credential isolation automatically. Agents never see your tokens. You can revoke access at any time.

When you use Axiom Skills, you configure API tokens directly. For detailed guidance on secure token configuration, see Token hygiene for AI agents.

Limit query costs

Query cost limits let you cap the hourly and daily query costs of an AI agent so it can query your data autonomously without creating unexpected costs. With MCP Server, the agent acts as your user account through OAuth, so set query cost limits on your roles.

For more information, see Set query cost limits for AI agents.

Use MCP Server

After setup, ask your agent about your data. For example:

• “List datasets.”
• “List the fields in the dataset logs.”
• “Get the most common status codes in the last 30 minutes in the dataset logs.”

Optional: use the prebuilt prompts in clients that support MCP prompts.

For more examples and the full tool list, see MCP tools reference.

Revoke access

To revoke access:

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

If you connected with the mcp-remote library, clear the .mcp-auth folder. On a Mac, the default path is ~/.mcp-auth.