mcp -axiom

This MCP server implementation exposes six MCP tools for querying and managing data in Axiom via the Model Context Protocol: queryApl to run APL queries against Axiom datasets, listDatasets to enumerate available datasets, getDatasetSchema to retrieve a dataset's schema, getSavedQueries to fetch saved or starred APL queries, getMonitors to list monitoring configurations, and getMonitorsHistory to view monitor execution history. All tools require a valid Axiom API token provided as the token parameter or via environment variables, and requests are authenticated against your Axiom tenant. You can configure the MCP server with a config file or environment variables, and wire it into clients such as Claude by specifying the server in the Claude MCP configuration.

To use the server, start the axiom-mcp binary with the appropriate configuration (e.g., a config.txt file) containing your token and endpoint details. The Claude integration example shows how to point Claude at the MCP server and provides an example JSON snippet for the mcpServers section, including optional environment variables for authentication and rate limiting.

Prerequisites:

• A supported environment (Linux, macOS) with Go installed if you are building from source, or prebuilt binaries available from releases.
• An Ax iom API token and the API URL for your tenant.

Install from releases (recommended):

1. Download the latest built binary from the releases page.
2. Place the binary somewhere on your PATH, e.g. /usr/local/bin/axiom-mcp
3. Create a config file (config.txt) with your credentials and rate settings, for example: token xaat-your-api-token url https://api.axiom.co query-rate 1 query-burst 1 datasets-rate 1 datasets-burst 1 monitors-rate 1 monitors-burst 1
4. Run the MCP server: axiom-mcp --config /path/to/config.txt

If building from source:

1. Ensure Go is installed (go1.20+ recommended).
2. Build the binary: go install github.com/axiomhq/axiom-mcp@latest
3. Run the server with your config as above.

Notes and tips:

• This MCP server is deprecated in favor of the official Axiom MCP Server. If you are starting fresh, consider using mcp.axiom.co instead.
• The server requires authentication via an API token. You can provide this token in a config file, as command-line flags, or via environment variables (AXIOM_TOKEN, AXIOM_URL).
• If you upgrade or migrate, ensure your token and endpoint URL are kept secure and not exposed in logs.
• The configuration supports per-tool rate limiting via query-rate, query-burst, datasets-rate, datasets-burst, monitors-rate, and monitors-burst.
• The configuration example uses a config.txt with token and URL; you can also provide these values via environment variables in the env block of the Claude integration configuration.