Get the FREE Ultimate OpenClaw Setup Guide →

mcp -axiom-js

MCP server from ThetaBird/mcp-server-axiom-js

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio thetabird-mcp-server-axiom-js npx -y mcp-server-axiom \
  --env AXIOM_URL="https://api.axiom.co" \
  --env AXIOM_TOKEN="<AXIOM_TOKEN_HERE>" \
  --env AXIOM_ORG_ID="<AXIOM_ORG_ID_HERE>"

How to use

This MCP server is a JavaScript port of the Axiom MCP server. It exposes an HTTP API that lets AI agents query Axiom data using Axiom Processing Language (APL) and list available datasets. The server can be run via npx, wiring in your Axiom credentials through environment variables or a configuration file. The main toolbox exposed by this server is two tools: queryApl, which executes APL queries against your Axiom datasets, and listDatasets, which returns the datasets you have access to. You can call these tools through the MCP tools API at the endpoints described in the README, enabling seamless integration with conversational agents or automated workflows that need to fetch or filter data from Axiom.

Once running, you can use POST requests to the tools endpoints to perform queries or data discovery. For example, queryApl accepts a JSON payload with a query field containing your APL expression, while listDatasets returns the available datasets. The server supports configuring rate limits and ports via environment variables or a config file, ensuring it can run reliably within your infrastructure.

How to install

Prerequisites:\n- Node.js and npm installed on your system.\n- Access to npm to install or run the MCP server.\n\nInstall steps:\n1) Install the MCP server package globally (optional, as you can also run via npx):\nbash\nnpm install -g mcp-server-axiom\n\n\n2) Run the MCP server using npx (as described in the configuration example):\nbash\nnpx -y mcp-server-axiom\n\n\n3) Alternatively, run by providing a configuration file (config.json) in the local directory or via your runtime environment:\nbash\nmcp-server-axiom config.json\n\n\n4) If you are configuring via environment variables, set AXIOM_TOKEN, AXIOM_URL, and AXIOM_ORG_ID before starting the server:\nbash\nexport AXIOM_TOKEN=your_token\nexport AXIOM_URL=https://api.axiom.co\nexport AXIOM_ORG_ID=your_org_id\nmcp-server-axiom\n\n\n5) Optional: adjust rate limits and port using the provided environment variables described in the README, such as AXIOM_QUERY_RATE, AXIOM_QUERY_BURST, AXIOM_DATASETS_RATE, AXIOM_DATASETS_BURST, and PORT.

Additional notes

Tips and common considerations:\n- Ensure AXIOM_TOKEN, AXIOM_ORG_ID, and AXIOM_URL are correctly set to access your Axiom data.\n- The defaults are AXIOM_URL=https://api.axiom.co and port 3000 if PORT is not specified.\n- If you run into authentication errors, double-check that the token has the required scopes for the datasets you intend to query.\n- The available tools are: queryApl (execute APL queries) and listDatasets (retrieve datasets). You can expand usage by combining the MCP server with your agent framework to orchestrate prompts and results from Axiom.\n- When using a config.json, align the field names with the JSON example in the README (token, url, orgId, queryRate, queryBurst, datasetsRate, datasetsBurst).

Related MCP Servers

Sponsor this space

Reach thousands of developers