Axiom MCP server for Claude, Codex and Cursor

What your AI apps can do with Axiom

Run APL queries
List datasets and monitors

Axiom MCP tools

31 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`queryDataset`	Run an APL query against an events or traces dataset (read-only)
`getSavedQueries`	Get the organization's saved APL queries (read-only)
`listDatasets`	List datasets you can access (read-only)
`getDatasetFields`	Get field names and types for an events or traces dataset (read-only)
`createDataset`	Create a dataset in the current organization
`listMetrics`	List metric names in a dataset (read-only)
`listMetricTags`	List tags available for filtering metrics (read-only)
`getMetricTagValues`	Get the values for a metric tag (read-only)
`searchMetrics`	Find metrics matching a known tag value (read-only)
`queryMetrics`	Run an MPL query against a metrics dataset (read-only)
`listDashboards`	List the organization's dashboards (read-only)
`getDashboard`	Get dashboard details by UID (read-only)
`exportDashboard`	Export a dashboard as JSON (read-only)
`createDashboard`	Create a dashboard from a JSON document
`updateDashboard`	Update a dashboard by UID
`updateDashboardChart`	Patch one dashboard chart by chart ID
`deleteDashboard`	Delete a dashboard by UID
`checkMonitors`	List monitors and their current status (read-only)
`getMonitor`	Get a monitor's full definition including query (read-only)
`getMonitorHistory`	Get a monitor's alert history (read-only)
`listNotifiers`	List configured notifiers (read-only)
`createMonitor`	Create a monitor
`updateMonitor`	Update a monitor by ID
`deleteMonitor`	Delete a monitor by ID
`createNotifier`	Create a notifier
`updateNotifier`	Update a notifier by ID
`deleteNotifier`	Delete a notifier by ID
`services-getMap`	Get the service dependency graph with volume, errors and latency (read-only)
`services-getChanges`	Report service graph changes such as new dependencies or regressions (read-only)
`services-getEdgeHistory`	Get time-series history for a service's dependency edges (read-only)
`sendFeedback`	Send feedback to Axiom about tools, results or missing features

Suggested access for each AI app

The documentation this list comes from doesn't mark Axiom's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Axiom connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Axiom to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Axiom tool, give Cursor only the read tools, or keep Axiom away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Axiom MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Axiom in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Axiom endpoint to each app separately. In Claude Code:

Shell

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

In Cursor's mcp.json:

JSON

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

Some servers accept only clients they have approved, or need a token header. Check the Axiom MCP documentation for what your client needs.

Before you connect

An Axiom account. Sign-in uses your Axiom permissions.

Server details

Detail	Value
Publisher	Axiom
Endpoint	`https://mcp.axiom.co/mcp`
Authentication	Browser sign-in
Categories	Development, Data & infrastructure
Tool list	31 tools, observed 29 October 2026 (docs)

Axiom MCP documentation