How to Use the Axiom MCP in Claude Code

Q: How do I add the Axiom MCP Server to Claude Code?

Run claude mcp add --transport http axiom-mcp -- to register the server in your terminal.

Q: Can Claude Code automate Axiom monitor creation?

Yes. Claude Code uses createmonitor to set up new threshold alerts based on your local script configurations.

Q: Is it possible to query Axiom logs headlessly with Claude Code?

Yes. Claude Code runs APL queries through runquery and outputs clean JSON directly to your terminal.

Q: How is my Axiom telemetry data secured in this CLI environment?

Your credentials stay in /.claude.json on your local machine. The Vinkius MCP Server sandbox acts as an ephemeral proxy, ensuring that your raw log payloads go directly to Axiom without middleman exposure.

Run APL queries, ingest logs, and manage Axiom monitors with Claude Code using this lightweight MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Axiom MCP to Claude Code

Create your Vinkius account to connect Axiom to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Axiom with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run terminal-based APL queries on Axiom datasets

The `run_query` tool executes raw APL queries against your Axiom datasets directly from the command line. You type a plain-English request, and Claude Code translates it into a precise query. Query results pipe directly to your terminal output as raw JSON. From there, grep or filter the output using standard terminal utilities.

CLI-driven Axiom monitor management via MCP Server

The `create_monitor` and `delete_monitor` tools let you maintain your alert configurations without leaving your SSH session. Your agent reads your local YAML configs and updates your remote monitors. This makes managing alert rules fast and scriptable. You can easily tear down staging monitors or spin up production alerts from a single terminal command.

Shell-integrated data ingestion

The `ingest_data` tool pushes system logs and script outputs directly into Axiom from Claude Code. You can pipe cron job failures or build logs straight to your active datasets. This eliminates the need for custom curl scripts in your CI pipeline. Your agent handles the ingestion handshake and formats the payload automatically.

Setup guide

Set up Axiom MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see axiom-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Axiom transactions." It will automatically discover and invoke the available Axiom tools.

Terminal

claude mcp add --transport http axiom-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Axiom MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "axiom-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Axiom. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Axiom now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Axiom MCP in Claude Code

Run `claude mcp add --transport http axiom-mcp -- ` to register the server in your terminal.

Yes. Claude Code uses `create_monitor` to set up new threshold alerts based on your local script configurations.

Yes. Claude Code runs APL queries through `run_query` and outputs clean JSON directly to your terminal.

Absolutely, you can run Claude Code in non-interactive environments to manage datasets and monitors.

Your credentials stay in `~/.claude.json` on your local machine. The Vinkius MCP Server sandbox acts as an ephemeral proxy, ensuring that your raw log payloads go directly to Axiom without middleman exposure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript