Kalmia MCP server
OfficialSupports tracing OpenAI SDK calls so OpenAI-powered agent runs can be collected in Kalmia for triage, verdicts, and issue investigation.
Supports OpenTelemetry trace ingestion, allowing applications instrumented with OpenTelemetry to send traces to Kalmia for monitoring and investigation.
Connects Kalmia monitoring to Slack, enabling issue digests and alerts to be sent to a chosen Slack destination through an approval-gated action.
Supports instrumenting the Vercel AI SDK so AI SDK runs can be traced and analyzed in Kalmia.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Kalmia for coding agents
Kalmia traces your AI agents and finds what went wrong. It triages every run, investigates failures down to the root cause, and alerts you.
This repository connects Kalmia to your coding agent. It contains two things:
The Kalmia MCP server. Your agent can query traces, read root-cause verdicts and grouped issues, compare variants and eval runs, and start investigations and sweeps.
The
kalmia-setupskill. Your agent adds Kalmia tracing to a codebase: it installs the SDK, wraps the LLM client, groups runs into traces, checks that a trace arrived, and sets up issue digests.
Kalmia works with OpenTelemetry, the Vercel AI SDK, the OpenAI and Anthropic SDKs, and plain HTTP.
Before you start
You need a Kalmia API key.
Sign up free, then create a read-and-write key under Settings > API keys.
It starts with kal_live_.
Related MCP server: Open Train MCP
Install
Claude Code
/plugin marketplace add KalmiaAI/kalmia-plugin
/plugin install kalmia@kalmiaClaude Code asks for your API key when the plugin is enabled.
The setup skill is then available as /kalmia:kalmia-setup.
To add only the MCP server, without the plugin:
claude mcp add --transport http kalmia https://www.kalmia.dev/api/mcp \
--header "Authorization: Bearer $KALMIA_API_KEY"Cursor
Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project, and set KALMIA_API_KEY in your environment:
{
"mcpServers": {
"kalmia": {
"url": "https://www.kalmia.dev/api/mcp",
"headers": { "Authorization": "Bearer ${env:KALMIA_API_KEY}" }
}
}
}Any agent that supports skills
npx skills add KalmiaAI/kalmia-pluginAny other MCP client
URL:
https://www.kalmia.dev/api/mcpTransport: streamable HTTP
Header:
Authorization: Bearer <your API key>
What the MCP server can do
Group | Tools |
Read your traces |
|
Read what Kalmia found |
|
Take action (each asks for your approval) |
|
Some actions use credits from your plan. See pricing.
Where your data goes
Everything goes to Kalmia's own service at www.kalmia.dev, and nowhere else.
The MCP server sends your agent's requests to
https://www.kalmia.dev/api/mcp, with your API key. It reads traces already stored in your Kalmia workspace. The action tools write back to that workspace: labels, investigations, and monitoring settings.The
kalmia-setupskill changes your codebase so your app sends its traces to Kalmia (https://www.kalmia.dev/api/v1/traces/ingest, orhttps://www.kalmia.dev/api/otel/v1/tracesfor OpenTelemetry). It sends one test request to check that a trace arrived. It installs the Kalmia SDK from npm or PyPI.Digests, if you turn them on, go to the email, Slack or Microsoft Teams destination you choose.
Traces can contain whatever your agent handled, including personal data. Kalmia keeps them for your workspace's retention period. See the privacy policy.
Things to try
"Set up Kalmia tracing in this repo."
"What are the most common issues in my agent's traces this week?"
"Why did trace
<id>fail? Show me the root cause and the suggested fix.""Compare failure rates between my two prompt variants."
Links
License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Errors, traces, replays and logs from Talaria for coding agents.
Run AI evaluations, record agent traces and gate releases on evidence, with scoped org access.
Read-only release evidence for coding agents: findings, deliveries, source and runtime data.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access observability and evaluation data, including run history, span traces, LLM-as-judge evaluation results, and regression reports.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to browse and filter experiment runs, retrieve metrics, logs, tables, and artifacts, plot comparisons as PNG images, and download full-fidelity training history for local analysis against a self-hosted Open Train server. It also provides diagnostic tooling that surfaces metric evidence and investigation leads without asserting causality.16MIT

squally-mcpofficial
AlicenseAqualityBmaintenanceEnables coding agents to read Squally CI data, including test results, flakiness, and failure diagnostics.7720 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to query trace, session, exception, prompt, dataset, score, and metric data for enhanced debugging and observability.-