OBSERVABILITY / Axiom
Axiom MCP
Queries Axiom telemetry and manages observability resources through an account-authorized hosted connection.
“Connect AI agents to Axiom with the Model Context Protocol (MCP) Server.”
01 / THE REASONING
Why this made the selection.
- Exposes APL queries and dataset exploration alongside observability resource tools.
- Uses the connected user’s role and permissions rather than granting access to all organization data.
- Axiom’s page describes a remote MCP server that uses OAuth so agents do not see the user’s tokens, with an API-token header path for agents that cannot use browser OAuth.
- Agents that do not support remote MCP are told to use a separate bridge, and the tools page only lists the exposed tools and prompts.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Official MCP setup, data-flow and permissions documentation
- Official tool reference
- https://axiom.co/docs/console/intelligence/mcp-server
- https://axiom.co/docs/console/intelligence/mcp-server/tools
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The current tools include both query and management actions; regional processing and account permissions are disclosed.
- The remote Axiom MCP server uses OAuth, and the page says that flow keeps credentials isolated so agents never see the tokens.
- If the agent does not support browser OAuth, the page says to authenticate with headers and an API token instead of OAuth 2.0.
- If the agent does not support remote MCP directly, the page points elsewhere rather than at the remote server alone. The tools page describes the exposed tools and prompts, including a way to send feedback about missing capabilities.
- The publisher says hosted MCP query results route through US infrastructure, including queries against a remote data deployment.
Not established by this review
- No MCP server or upstream package was installed or run.
- No authenticated account, client handshake, query, write operation or security test was performed.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add https://mcp.axiom.co/mcp as a remote HTTP MCP server.
- Complete OAuth with the intended Axiom organization and review the user’s role and dataset permissions.
- Start with a narrow query; approve any resource-management action separately.
Before you start
- An Axiom account with the relevant dataset and resource permissions
- An OAuth-capable remote MCP client
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"servers": {
"axiom": {
"type": "http",
"url": "https://mcp.axiom.co/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://axiom.co/docs/console/intelligence/mcp-server
Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review
- Axiom tool reference ↗Checked
https://axiom.co/docs/console/intelligence/mcp-server/tools
Supports: review, limitations, access