LabscoMCP early access ↗
axiomhqMCP SERVER · OFFICIAL PROJECT

Axiom

Query your Axiom event data in APL, then build the dashboard and monitor that came out of the answer.

by axiomhq ↗Observability, Monitoring & Incident Response✓ Official

No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.

View project ↗

LABSCO SUMMARY

Ask what broke, then ship the monitor that catches it next time.

Most observability connections stop at read access. This one closes the loop: the agent investigates in APL, then creates the dashboard chart and the monitor in the same conversation. Query cost limits are the guardrail that makes letting it run unattended reasonable.

What it is

Axiom hosts this server at https://mcp.axiom.co/mcp. An agent gets your datasets, the APL query engine, and the dashboard, monitor and notifier objects around them.

What you get

  • queryApl and queryMetrics run queries against your datasets; listDatasets and getDatasetSchema tell the agent what is there
  • Dashboards created, updated, exported and deleted — updateDashboardChart patches a single chart by its ID instead of rewriting the whole document
  • Monitors and notifiers created, updated and deleted, with checkMonitors for current status and getMonitorHistory for past alerts
  • Metric discovery through listMetrics, listMetricTags, getMetricTagValues and searchMetrics
  • Prebuilt prompts for anomaly detection, data quality investigation, performance baselines, cross-dataset correlation, monitor health and exploring a dataset nobody knows

Requirements

An Axiom account. The hosted endpoint uses OAuth and agents never see your token; an agent that cannot do browser OAuth sends a personal access token plus the organization ID as headers. Hosted query results route through US infrastructure.

Setup effort

Add the hosted endpoint, then sign in — paste it into your client, then approve the OAuth sign-in