MCP server
by thetabird
Integrate with Axiom to run APL queries, analyze logs, detect anomalies, and make data-driven decisions easily.
Connects to Axiom to execute APL queries and manage datasets. Enables AI agents to perform log analysis and anomaly detection on your Axiom data.
Axiom is a community-built MCP server published by thetabird that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Axiom to run APL queries, analyze logs, detect anomalies, and make data-driven decisions easily. It is categorized under analytics data.
You can install Axiom in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Axiom is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Axiom is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Axiom against two servers with overlapping tools; this profile had the clearer scope statement.
Axiom is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Axiom has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: Axiom surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Axiom benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Axiom reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Axiom is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Axiom for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Axiom is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 35
A JavaScript port of the official Axiom MCP server that enables AI agents to query data using Axiom Processing Language (APL).
<a href="https://glama.ai/mcp/servers/8hxxw8uenu"> <img width="380" height="200" src="https://glama.ai/mcp/servers/8hxxw8uenu/badge" /> </a>This implementation provides the same functionality as the original Go version but packaged as an npm module for easier integration with Node.js environments.
You can run this MCP server directly using npx. Add the following configuration to your MCP configuration file:
{
"axiom": {
"command": "npx",
"args": ["-y", "mcp-server-axiom"],
"env": {
"AXIOM_TOKEN": "<AXIOM_TOKEN_HERE>",
"AXIOM_URL": "https://api.axiom.co",
"AXIOM_ORG_ID": "<AXIOM_ORG_ID_HERE>"
}
}
}
npm install -g mcp-server-axiom
The server can be configured using environment variables:
AXIOM_TOKEN (required): Your Axiom API tokenAXIOM_ORG_ID (required): Your Axiom organization IDAXIOM_URL (optional): Custom Axiom API URL (defaults to https://api.axiom.co)AXIOM_QUERY_RATE (optional): Queries per second limit (default: 1)AXIOM_QUERY_BURST (optional): Query burst capacity (default: 1)AXIOM_DATASETS_RATE (optional): Dataset list operations per second (default: 1)AXIOM_DATASETS_BURST (optional): Dataset list burst capacity (default: 1)PORT (optional): Server port (default: 3000)export AXIOM_TOKEN=your_token
mcp-server-axiom
mcp-server-axiom config.json
Example config.json:
{
"token": "your_token",
"url": "https://custom.axiom.co",
"orgId": "your_org_id",
"queryRate": 2,
"queryBurst": 5,
"datasetsRate": 1,
"datasetsBurst": 2
}
GET /: Get server implementation infoGET /tools: List available toolsPOST /tools/:name/call: Call a specific tool
queryApl: Execute APL querieslistDatasets: List available datasetscurl -X POST http://localhost:3000/tools/queryApl/call \
-H "Content-Type: application/json" \
-d '{
"arguments": {
"query": "['logs'] | where ['severity'] == "error" | limit 10"
}
}'
curl -X POST http://localhost:3000/tools/listDatasets/call \
-H "Content-Type: application/json" \
-d '{
"arguments": {}
}'
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.