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 VS Code Copilot?
GitHub Copilot Agent mode brings Axiom data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 31 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Axiom in VS Code Copilot
Axiom and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Axiom to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
TimezoneDB
5 toolsManage global time — audit timezones and offsets via AI.

MonkeyLearn
12 toolsAnalyze text data with custom machine learning models that classify sentiment, extract keywords, and tag topics automatically.

AppTweak
9 toolsBring App Store Optimization (ASO) to your AI agent — track app rankings, fetch keyword volumes, and analyze competitor downloads via chat.

Evisort Contract Intelligence
10 toolsEquip your AI agent to manage contract documents, track AI-extracted provisions, and monitor workflows via the Evisort API.
