Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Axiom MCP Server for Claude

Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server.

by Axiom, Inc.·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming.
  • APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota.

Privacy notes

  • Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context.
  • OAuth is the recommended authentication method — no API token is stored in your MCP configuration.

Prerequisites

  • An Axiom account — authenticate via OAuth when prompted in Claude Code, or generate an API token in Axiom settings.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}

About this resource

Overview

The Axiom MCP Server is the official remote Model Context Protocol server from Axiom. It connects Claude to your Axiom observability data — datasets, dashboards, monitors, metrics, and saved queries — through 18 tools built around Axiom's APL (Axiom Processing Language) query engine.

With the MCP server, Claude can run ad-hoc APL queries over your log data, inspect dashboard definitions, check monitor status, and browse dataset schemas without leaving your IDE.

Authentication uses OAuth (recommended) or an Axiom API token.

Key capabilities

  • APL queries — execute queryApl and queryMetrics for ad-hoc analytics over any dataset.
  • Dataset exploration — list datasets, introspect schemas, and retrieve field metadata.
  • Dashboards — list, get, create, update, and delete dashboards.
  • Monitors — list monitors and retrieve execution history.
  • Metrics — list metrics, tags, and tag values for metric discovery.
  • Saved queries — retrieve starred APL queries from your workspace.

Tools

Tool Purpose
queryApl Execute an APL query against a dataset
queryMetrics Query metric data with filtering
listDatasets List all available datasets
getDatasetSchema Introspect dataset field schema
listMetrics List defined metrics
listMetricTags / getMetricTagValues / searchMetrics Metric discovery
createDashboard / getDashboard / listDashboards / updateDashboard / deleteDashboard Dashboard CRUD
getMonitors / getMonitorsHistory Monitor status and history
getSavedQueries Retrieve saved/starred queries

How it compares

Server APL/custom queries Dashboards Monitors Metrics Auth
Axiom MCP Yes (APL) Yes Yes Yes OAuth / API token
Grafana MCP Limited Yes Yes Yes API key
Datadog MCP Metrics + logs Yes Yes Yes API key
Honeycomb MCP Yes (BubbleUp) Limited Yes Yes OAuth / API key

Axiom's APL is a powerful columnar query language for log analytics, making the MCP server well-suited for ad-hoc investigation queries over structured log and trace datasets.

Installation

Claude Code (OAuth — recommended)

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

Run /mcp in Claude Code to authenticate via OAuth.

Claude Code (API token)

claude mcp add --transport http axiom "https://mcp.axiom.co/mcp?org-id=YOUR_ORG_ID" \
  --header "Authorization: Bearer YOUR_AXIOM_API_TOKEN"

Claude Desktop

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

Alternative endpoint

For clients requiring server-sent events, use https://mcp.axiom.co/sse instead of the streamable HTTP endpoint.

Requirements

  • An Axiom account.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • OAuth authentication minimizes credential exposure.
  • API tokens can be scoped to specific permissions and rotated from Axiom settings.

Source Verification Notes

Verified on 2026-06-18:

  • Axiom's MCP documentation at axiom.co/docs/console/intelligence/mcp-server confirms the hosted endpoints, OAuth + API token auth, and the 18-tool surface including APL query, dashboard management, and monitor tools.
  • Axiom's APL documentation at axiom.co/docs/apl documents the query language used by queryApl and related query tools.
  • GitHub repo axiomhq/mcp (MIT) is the open-source Cloudflare Workers reference implementation.
#axiom#observability#log-analytics#apl#monitoring#dashboards#telemetry

Source citations

Add this badge to your README

Show that Axiom MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/axiom-mcp-server.svg)](https://heyclau.de/entry/mcp/axiom-mcp-server)

How it compares

Axiom MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldAxiom MCP Server for Claude

Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server.

Open dossier 		Pydantic Logfire MCP Server for Claude

Query OpenTelemetry traces and metrics, manage dashboards, analyze distributed traces, and investigate exceptions from Claude — with the official Pydantic Logfire remote MCP server hosted at logfire-us.pydantic.dev/mcp.

Open dossier 		Amplitude MCP Server for Claude

Official remote MCP server for querying and creating Amplitude analytics, dashboards, experiments, cohorts, session replay insights, and product data from Claude and other MCP clients.

Open dossier 		Brex MCP Server for Claude

Manage your Brex corporate card and banking account from Claude — expenses, cards, transactions, users, bills, vendors, travel bookings, and spend analytics — with the official Brex remote MCP server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorAxiom, Inc.PydanticAmplitudeBrex
Added2026-06-182026-06-182026-06-052026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming. APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota.✓Telemetry data returned by the MCP server may include user-controlled content from traces, logs, exceptions, model payloads, tool arguments, and tool results — treat query results as diagnostic data, not instructions. Dashboard create, update, and delete operations permanently modify your Logfire workspace; review before confirming.✓The authenticated Amplitude MCP server can expose tools that create and edit analytics content, not just read existing dashboards. Use the existing Amplitude permission model and keep users scoped to the projects and organizations they are allowed to inspect. Require human confirmation before Claude creates dashboards, edits notebooks, changes experiments, creates cohorts, updates metrics, or touches feature-flag workflows. Use the EU MCP endpoint only when the Amplitude data resides in the EU region; otherwise use the standard US endpoint. Consider progressive discovery to reduce tool-list size and force the assistant to describe a tool schema before calling higher-impact tools. Organization administrators can restrict or disable MCP access in Amplitude content access settings; use that control if AI access is not approved.✓Each tool requires specific Brex user capabilities — access is constrained by your existing Brex account permissions and team policies. This MCP server provides read and write access to financial data including expenses, cards, and transactions; confirm any write operations before approving. API key auth should use a token scoped to the minimum required permissions; rotate keys regularly from Settings → Developer.
Privacy notes✓Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.✓OpenTelemetry trace data, span metadata, exception stack traces, query results, dashboard configurations, and project metadata from your Logfire account are surfaced in Claude's context. Remote MCP uses OAuth — no API keys in your MCP config when authenticating via browser. For API key auth, store the key in MCP config rather than shell history.✓Amplitude MCP can expose product analytics, event data, user cohorts, experiment results, dashboard definitions, session replay context, feedback summaries, AI agent analytics, and account health signals to the connected AI client. AI providers may process the Amplitude data returned through MCP; review internal AI, privacy, GDPR, CCPA, and customer-data policies before connecting production projects. Assistant transcripts, MCP client logs, screenshots, support tickets, and exported chats can retain user identifiers, cohort definitions, behavioral data, experiment details, and roadmap-sensitive product insights. OAuth ties access to the current Amplitude user, but it does not make downstream model transcripts private by itself.✓Expense details, card data, banking transactions, user profiles, and vendor information from your Brex workspace are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.
Prerequisites
  • An Axiom account — authenticate via OAuth when prompted in Claude Code, or generate an API token in Axiom settings.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Pydantic Logfire account — authenticate via browser OAuth on first use (no API key required).
  • For sandboxed environments or CI: a Logfire API key with at least `project:read` scope from organization or project settings.
  • EU region users: use `https://logfire-eu.pydantic.dev/mcp` instead of the US endpoint.
  • An MCP client such as Claude Code or Claude Desktop.
  • Existing Amplitude customer account with access to the projects you want Claude to analyze.
  • MCP-capable client that supports remote Streamable HTTP servers, such as Claude Code, Cursor, ChatGPT, Codex CLI, Lovable, Kiro, or another compatible client.
  • OAuth authorization through Amplitude for the user and organization being queried.
  • Organization-level MCP access left enabled by an Amplitude administrator.
  • A Brex account — authenticate via OAuth (recommended) when prompted, or generate a Bearer API key in Settings → Developer.
  • Permissions in your Brex workspace aligned with the data you need (expenses, cards, banking).
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add --transport http axiom https://mcp.axiom.co/mcp
claude mcp add logfire --transport http https://logfire-us.pydantic.dev/mcp
claude mcp add -t http -s user amplitude https://mcp.amplitude.com/mcp
claude mcp add --transport http brex https://api.brex.com/mcp
Config
{
  "mcpServers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
{
  "mcpServers": {
    "logfire": {
      "type": "http",
      "url": "https://logfire-us.pydantic.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LOGFIRE_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "amplitude": {
      "url": "https://mcp.amplitude.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "brex": {
      "type": "http",
      "url": "https://api.brex.com/mcp"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.