# Axiom MCP server

> Run APL queries over logs, traces and events in Axiom, and explore datasets, dashboards and monitors from your assistant.

- Listing: https://mcp.tc/i/axiom
- Connect: use the server's own URL `https://mcp.axiom.co/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: Axiom
- Homepage: <https://axiom.co/docs/console/intelligence/mcp-server>
- Repository: <https://github.com/axiomhq/mcp/tree/HEAD/apps/mcp>

## About

Connects your AI assistant to Axiom so it can query event data with Axiom Processing Language (APL). It can list datasets and schemas, explore metrics, and manage dashboards, monitors and notifiers. Prebuilt prompts cover exploration, anomaly investigation and monitoring.

Runs as a hosted remote server at https://mcp.axiom.co/mcp using streamable HTTP, with an SSE endpoint also listed. You sign in with OAuth in the browser and need an Axiom account and a dataset. The hosted server is located in the US, so query results route through US infrastructure.

## What it can do

- Run APL queries over logs, traces and events
- List datasets and inspect their schemas
- Explore datasets and metrics
- Manage dashboards, monitors and notifiers
- Use prebuilt prompts for exploration, anomalies and monitoring

## Example prompts

- "List the datasets in my Axiom organization."
- "Run an APL query for 5xx errors in the last hour."
- "Show the schema of my production logs dataset."
- "Look for anomalies in request latency since yesterday."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http axiom https://mcp.axiom.co/mcp
```

2. Start Claude Code, type `/mcp`, pick **axiom** and choose **Authenticate**. A browser window opens for the Axiom sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Axiom** and paste this URL:

```url
https://mcp.axiom.co/mcp
```

3. Click **Add**, then **Connect**, and sign in when Axiom asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Axiom&connectorUrl=https%3A%2F%2Fmcp.axiom.co%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.axiom.co/mcp` and click **Add**.

3. Click **Connect** and sign in when Axiom asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.axiom.co/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Axiom to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=axiom&config=eyJ1cmwiOiJodHRwczovL21jcC5heGlvbS5jby9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "axiom": {
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=axiom&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.axiom.co%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"axiom","type":"http","url":"https://mcp.axiom.co/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "axiom": {
      "serverUrl": "https://mcp.axiom.co/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add axiom --url https://mcp.axiom.co/mcp
codex mcp login axiom
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.axiom]
url = "https://mcp.axiom.co/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http axiom https://mcp.axiom.co/mcp
```

Then, inside Gemini CLI, run `/mcp auth axiom` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.axiom.co/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/axiom (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report