AXIOM MCP SERVER

Connect Axiom to Andromity with the Axiom MCP server

Connect Axiom's official MCP server to Andromity: let your AI coding agent run APL queries, inspect datasets and metrics, and manage dashboards and monitors.

Server
https://mcp.axiom.co/mcp
Connects with
Browser sign-in (OAuth)
Category
Monitoring

Axiom hosts an official MCP server at https://mcp.axiom.co/mcp. With it, Andromity can run APL queries against your event and trace datasets, inspect fields and metrics, and check monitors while it debugs your code.

Sign-in is OAuth in your browser, and the agent acts as your Axiom user.

What the agent can do with Axiom

  • Run APL queries on events and traces datasets (queryDataset) and list saved queries (getSavedQueries).
  • List datasets and their fields (listDatasets, getDatasetFields).
  • Query metrics (listMetrics, queryMetrics, searchMetrics).
  • Read, create and update dashboards (getDashboard, createDashboard, updateDashboard).
  • Check monitors, their definitions and alert history (checkMonitors, getMonitor, getMonitorHistory).
  • Manage monitors and notifiers (createMonitor, updateMonitor, createNotifier).
  • Read the service dependency graph when service map is enabled (services-getMap).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Axiom MCP server”.

  • Run an APL query on the api-logs dataset for 500 errors in the last hour, group them by route and point me to the handlers in this repo.
  • Check which Axiom monitors are alerting and tell me whether this branch touches the code behind them.
  • List the fields in the traces dataset and make sure the span attributes we add in this PR match them.
  • Create an Axiom monitor for the error query we just wrote.

Connect Axiom

  1. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Axiom and select Connect.
  2. Sign in to Axiom in your browser and approve the connection.
  3. Andromity saves Axiom to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

  • With OAuth, the agent acts as your user account. Axiom says to set query cost limits (hourly and daily) on your roles for remote use.
  • Tools such as createDashboard, updateMonitor and deleteMonitor change data. Andromity's TRUST mode asks before tool calls whose names contain create, update or delete, and SAFE mode asks before every call.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

  • The remote server is hosted in the US, so query results route through US infrastructure.
  • Axiom's services-* tools need service map to be enabled.
  • Axiom documents header-based sign-in with a personal access token and an org ID for agents that cannot use browser OAuth; Andromity's one-click connector uses OAuth.

Questions

Does Axiom have an official MCP server?
Yes. Axiom hosts it at https://mcp.axiom.co/mcp and documents it in its console docs.
Does the Axiom MCP server need an API token?
Not with OAuth. You sign in through the browser. Axiom documents personal access tokens only for agents that cannot do browser sign-in.
Does Andromity use the Axiom SSE endpoint?
No. Axiom lists https://mcp.axiom.co/sse as a legacy endpoint; Andromity uses /mcp.

Sources

This guide is based on Axiom’s own documentation. The app controls its server, so tools can change; check the source for the current list.

Axiom is a trademark of its owner. Andromity is not affiliated with or endorsed by Axiom.