Compatible with every major AI agent and IDE
What is the Axiom MCP Server?
Connect your Axiom account to any AI agent to streamline your observability and log management workflows through natural conversation.
What you can do
- Data Ingestion & Querying — Ingest JSON, NDJSON, or CSV data and run complex Axiom Processing Language (APL) queries to analyze logs in real-time.
- Dataset Management — List, create, and update datasets to organize your telemetry and infrastructure data efficiently.
- Monitoring & Alerts — Manage monitors and notifiers to stay informed about system performance, errors, and anomalies.
- Dashboards & Annotations — Access dashboards and create annotations to visualize trends and mark significant system events.
- Organization Insights — Retrieve user information, API tokens, and organization details to maintain secure and authorized access.
How it works
- Subscribe to this server
- Enter your Axiom API Token and optional Organization ID
- Start analyzing your logs and managing infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps & SREs — instantly query logs for errors, check monitor statuses, and manage alerts without leaving the terminal or chat.
- Software Engineers — debug production issues by running APL queries directly from the code editor to find specific trace IDs or logs.
- Data Analysts — ingest and analyze large datasets using Axiom's powerful processing language through simple natural language prompts.
Built-in capabilities (31)
Create a new annotation
Create a new dashboard
Create a new dataset
Create a new monitor
Create a new notifier
Delete an annotation
Delete a dashboard
Delete a dataset
Delete a monitor
Delete a notifier
Retrieve a specific annotation by ID
Retrieve a specific dashboard by UID
Retrieve a specific dataset by ID
Retrieve a specific monitor by ID
Retrieve a specific notifier by ID
Retrieve an organization by ID
Retrieve a specific user by ID
Ingest data into an Axiom dataset
List all annotations
List all dashboards
List all datasets
List all monitors
List all notifiers
List all API tokens
List all users
Run an APL query against Axiom data
Update an existing annotation
Update an existing dashboard
Update an existing dataset
Update an existing monitor
Update an existing notifier
Why Cursor?
Cursor's Agent mode turns Axiom into an in-editor superpower. Ask Cursor to generate code using live data from Axiom and it fetches, processes, and writes. all in a single agentic loop. 31 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Axiom in Cursor
Axiom and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Axiom to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Axiom in Cursor
The Axiom MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 31 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Axiom for Cursor
Every tool call from Cursor to the Axiom MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I run complex log analysis using Axiom Processing Language (APL)?
Yes! Use the run_query tool to execute any APL string. You can specify start_time and end_time to filter your data and get precise analytical results directly in the chat.
How do I send new log data to my Axiom datasets?
You can use the ingest_data tool. Simply provide the dataset_name, the data payload, and the content_type (JSON, NDJSON, or CSV) to stream data into your Axiom account.
Is it possible to manage system monitors and alerts through this integration?
Absolutely. You have access to a full suite of tools including list_monitors, create_monitor, and update_monitor to configure threshold or anomaly detection alerts based on your APL queries.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Transistor.fm
11 toolsHost your podcast with analytics, multiple show support, and distribution to Apple Podcasts, Spotify, and every major platform.

Factor (Cofactr)
11 toolsAutomate supply chain operations via Factor (Cofactr) — manage parts, purchase orders, and inventory directly through your AI agent.

GlassFrog
12 toolsManage Holacracy circles, roles, and tactical projects via AI agents with GlassFrog.

Epsilon3 Aerospace Operations
10 toolsEquip your AI agent to manage operational procedures, track execution runs, and monitor telemetry via the Epsilon3 API.
