Axiom Remote MCP Server
Axiom's MCP server puts log and event analytics in agent hands โ query datasets with APL, monitor dashboards and investigate incidents across your observability data. Endpoint verified live on RemoteMCP.net (preflighted 401 OAuth challenge).
- Provider
- Axiom โ
- Categories
- โ๏ธ Cloud, Infrastructure & DevOps
ไธญๆ็ฎไป
Axiom ๅฎๆนๆ็ฎก็่ฟ็จ MCP ๆๅกๅจใAxiom MCP ๆๅกๅจ๏ผไธบไปฃ็ๆไพๆฅๅฟไธไบไปถๅๆ่ฝๅ๏ผAPL ๆฅ่ฏขใไปช่กจ็็ๆงไธไบไปถๆๆฅใ
Maintainer of Axiom? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"axiom": {
"url": "https://mcp.axiom.co/mcp"
}
}
}claude mcp add --transport http axiom https://mcp.axiom.co/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"axiom": {
"type": "http",
"url": "https://mcp.axiom.co/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.axiom.co/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"axiom": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.axiom.co/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"axiom": {
"serverUrl": "https://mcp.axiom.co/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"axiom": {
"url": "https://mcp.axiom.co/mcp"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.axiom] url = "https://mcp.axiom.co/mcp"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"axiom": {
"type": "streamableHttp",
"url": "https://mcp.axiom.co/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"axiom": {
"httpUrl": "https://mcp.axiom.co/mcp"
}
}
}๐งฐ Axiom MCP Tools & Schema (0)
| Tool | Safety | Description | Parameters |
|---|
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ
- PKCE S256
- โ Supported
- Protected resource metadata
- https://mcp.axiom.co/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Axiom MCP Endpoint Overview & Security Guide
Axiom โ Remote MCP Server
Axiom's MCP server puts log and event analytics in agent hands โ query datasets with APL, monitor dashboards and investigate incidents across your observability data. The remote endpoint means there is nothing to install โ point your MCP client at the URL and complete the OAuth consent screen. Axiom operates and versions the server themselves, so tool coverage tracks their API surface as it ships.
Official Axiom Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.axiom.co/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Axiom does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Axiom uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE โ and simply open a browser consent screen.
All 0 cataloged tools are read-only โ Axiom cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely.
๐ How to Connect
- Copy the Axiom endpoint URLThe remote endpoint is https://mcp.axiom.co/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http axiom https://mcp.axiom.co/mcp. Cursor: add"axiom": { "url": "https://mcp.axiom.co/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Axiom consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.axiom.co/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Axiom's 0 tools respond.
โ FAQ
What is the Axiom remote MCP endpoint?
The primary endpoint is https://mcp.axiom.co/mcp. It is an official first-party server operated by Axiom, speaking the Streamable HTTP transport.
How do I authenticate with Axiom?
Axiom uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen.
I'm getting a 401 Unauthorized from Axiom โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Axiom?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http axiom https://mcp.axiom.co/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Axiom expose?
0 tools are cataloged in this directory โ including . Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
AWS Knowledge's hosted remote MCP server. AWS's fully-managed public knowledge MCP gives agents access to the latest AWS documentation, API references, What's New posts and architectural guidance across all AWS services. It is public and unauthenticated โ connect and call tools immediately.
Cloudflare's free, authless documentation MCP server. Agents can search the full Cloudflare docs corpus โ no account or token required.
Vercel's official remote MCP server. Agents can list deployments, fetch build logs and search Vercel docs with a token-authorized connection.
Sentry's hosted MCP server for error monitoring. Agents can inspect issues, search events and resolve regressions directly from your IDE.