Axiom

Provides an MCP server to run Axiom queries via APL and list datasets.

javascript

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-thetabird_mcp-server-axiom-js": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-axiom"
      ],
      "env": {
        "PORT": "3000",
        "AXIOM_URL": "https://api.axiom.co",
        "AXIOM_TOKEN": "<AXIOM_TOKEN_HERE>",
        "AXIOM_ORG_ID": "<AXIOM_ORG_ID_HERE>",
        "AXIOM_QUERY_RATE": "1",
        "AXIOM_QUERY_BURST": "1",
        "AXIOM_DATASETS_RATE": "1",
        "AXIOM_DATASETS_BURST": "1"
      }
    }
  }
}

You can run and use the Axiom MCP Server in a Node.js environment to query data with APL and manage datasets. This server port mirrors the official MCP functionality, packaged as an npm module for easy integration with your Node workflows. It exposes endpoints for querying APL and listing datasets through a lightweight MCP interface.

How to use

You interact with the Axiom MCP Server by launching it as a local process and then sending tool calls from your MCP client. The server provides tools to execute APL queries and to list available datasets. Use the client’s standard MCP call mechanism to invoke the tools by name and pass the required arguments. Your client will receive results from the server and can handle them in your application flow.

How to install

Prerequisites you need before starting:
- Node.js and npm installed on your machine
- Basic familiarity with running commands in your shell

Follow this step-by-step flow to install and run the server locally.

# Global installation of the MCP server package
npm install -g mcp-server-axiom

# Run the server directly with environment variables (example)
export AXIOM_TOKEN=your_token
export AXIOM_ORG_ID=your_org_id
export AXIOM_URL=https://api.axiom.co
mcp-server-axiom

# Alternatively, use a configuration file to start the server
# Create a config.json with the required fields (see config example below)
mcp-server-axiom config.json

Configuration and usage notes

The server can be configured via environment variables or a configuration file. The example below shows how to configure the MCP entry for Axiom with an npx-based runtime. This setup uses an MCP command that launches the server as a child process and passes required credentials through environment variables.

{
  "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>"
    }
  }
}

Notes on environment variables and defaults

You can tune request rates and timeouts using these environment variables if your deployment uses the Axiom API. The defaults assume safe, conservative limits suitable for development and testing.

Additional sections

Security: Treat AXIOM_TOKEN as a secret. Do not commit it to source control. Use environment variable management practices appropriate for your environment. If you deploy to a cloud or orchestration system, prefer secret stores or encrypted environment management.

Available tools

queryApl

Execute APL queries against the Axiom data sources via the MCP server. Pass a query string and receive results back from the Axiom API.

listDatasets

Retrieve the list of available datasets from Axiom. Use this to discover what data you can query or integrate into your workflows.

Built by

VeilStrat

AI signals for GTM teams