MCP server · Engineering and operations

Axiom MCP server

Axiom in any MCP client, through Memtro: Axiom does not publish this server. Memtro's Axiom connector reads Axiom through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Query Axiom event and log data with APL, list datasets, monitors and what they notified, and read chart annotations. Can add, edit and delete annotations, create, change and delete monitors, and create, re-retain, trim and delete datasets when you ask.

Reads

  • axiom_list_datasetsDatasets in Axiom: name, description and when created.
  • axiom_queryRuns an APL query over Axiom data and returns rows.
  • axiom_list_monitorsMonitors in Axiom: name, description, type (threshold, match event, anomaly), whether disabled and until when, how often it runs…
  • axiom_monitor_historyWhat one monitor notified over a period (default the last 7 days), newest first: triggered or resolved, and when.
  • axiom_list_annotationsAnnotations on Axiom charts (deploys, incidents and other markers) over a period of at most 100 days (default the last 30), newest first: type…

Acts, when you ask

These change something in Axiom. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • axiom_create_annotationAdds an annotation (a marker such as a deploy or an incident) to the charts of one or more Axiom datasets.
  • axiom_update_annotationEdit an Axiom chart annotation.
  • axiom_delete_annotationPermanently delete an Axiom chart annotation; it disappears from every chart it was on.
  • axiom_create_monitorCreate an Axiom monitor that runs an APL query on a schedule and alerts the notifiers named (none unless given) when it fires.
  • axiom_update_monitorChange an Axiom monitor, e.g. disable or re-enable it, change its query, threshold or interval, or which notifiers it alerts…
  • axiom_delete_monitorPermanently delete an Axiom monitor and its label assignments; it stops running and alerting.
  • axiom_create_datasetCreate an empty Axiom dataset (name unique in the organisation).
  • axiom_update_datasetChange an Axiom dataset's description or retention.
  • axiom_trim_datasetPermanently delete every event older than the given number of days from one Axiom dataset.
  • axiom_delete_datasetDelete an Axiom dataset and queue the permanent deletion of all its events.

Connect it

First connect Axiom on Dashboard → Connections, then add Memtro to your client once. The Axiom tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Axiom connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › How many errors did the API log in the last hour?
  • › Show the recent failures for the billing service since the deploy
  • › Which monitors triggered this week, and when did they resolve?
  • › Add a deploy annotation for release 4.12 to the app dataset
  • › Disable the checkout latency monitor until Monday

Questions

Is this an official Axiom MCP server?
No. It is Memtro's MCP server with Memtro's Axiom connector behind it: the connector reads Axiom through its API with the credentials you connect on Dashboard → Connections, and Axiom publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Axiom?
Only when you ask, and only what it has been granted: add an annotation to one or more datasets' charts; edit an annotation; delete an annotation (permanent); create a monitor that alerts named notifiers; change, disable or re-enable a monitor; delete a monitor (permanent); create a dataset; change a dataset's description or retention (shorter retention removes older data); trim a dataset's events older than a number of days (permanent); delete a dataset and all its data (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time