runmeter
An MCP server that provides cost and reliability observability for LLM and agent workflows. It records model calls and allows querying and aggregating telemetry data through MCP tools.
README
runmeter
An MCP server that gives any LLM or agent workflow cost and reliability observability for free.
Record one row per model call (model, tokens, cost, latency, finish reason, tags), then query and aggregate that telemetry through MCP tools. Cost is computed automatically from a built-in, overridable pricing table when you do not pass an explicit figure. Storage is a local SQLite file. No external service, no credentials, no network calls.
Built with FastMCP. Works with any MCP client (Claude Code, Claude Desktop, or your own agent) over stdio.
Companion project: a-agentic-delivery-pipeline is an AI-native, skills-driven delivery pipeline that emits its per-stage telemetry to runmeter.
Why
Most agent stacks can tell you what an agent did, but not what it cost or how often it failed. Teams end up bolting on a spreadsheet or a bespoke logging table per project. runmeter makes per-run cost and reliability a first-class, queryable signal that every agent on the machine writes to the same way. It is the "cost-per-task economics" and "evaluation and performance" discipline that production agent work needs, packaged as a drop-in MCP server.
Tools
| Tool | Purpose | Hint |
|---|---|---|
runmeter_record |
Record one model/agent run; auto-computes cost when the model is priced | write |
runmeter_get |
Fetch a single run by id | read-only |
runmeter_list |
List runs newest-first with filters (model, agent, tag, status, since) and paging | read-only |
runmeter_summary |
Roll up cost, tokens, avg latency, and error rate grouped by model / agent / finish_reason / day / tag | read-only |
runmeter_export |
Export raw runs as JSON or CSV for external analysis | read-only |
runmeter_delete |
Delete one run by id; requires confirm=true |
destructive |
Every tool returns both a human-readable note and structured content.
Install
git clone https://github.com/Aptica-Solutions/a-mcp-runmeter.git
cd a-mcp-runmeter
python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
Run
python3 server.py
Connect from an MCP client
Point your client at server.py over stdio. Example (claude_mcp_config.json):
{
"mcpServers": {
"runmeter": {
"command": "python3",
"args": ["/absolute/path/to/a-mcp-runmeter/server.py"],
"env": { "RUNMETER_DB_PATH": "~/.runmeter/runmeter.db" }
}
}
}
Configuration
All optional. runmeter runs with zero configuration.
| Variable | Default | Purpose |
|---|---|---|
RUNMETER_DB_PATH |
~/.runmeter/runmeter.db |
SQLite telemetry store location |
RUNMETER_PRICING |
built-in table | JSON file overriding/extending per-model pricing |
Pricing override file shape (USD per 1,000,000 tokens):
{
"my-fine-tuned-model": { "input": 3.0, "output": 15.0 }
}
The built-in table ships sensible list-price defaults for common Claude, GPT, and Gemini models. They are convenience defaults, not a billing source of truth; override them for anything you meter seriously.
Example flow
An agent records each call as it goes:
// runmeter_record
{ "run": { "model": "claude-sonnet-4", "input_tokens": 8200, "output_tokens": 640,
"latency_ms": 1830, "finish_reason": "stop", "agent": "discharge-summarizer",
"tags": ["prod", "east"] } }
// -> cost auto-computed at $3/M in + $15/M out = $0.034200
Then you ask for a rollup:
// runmeter_summary { "group_by": "model", "since": "7d" }
// -> per-model run count, tokens, total cost, avg latency, and error rate,
// sorted by cost descending, with grand totals.
since accepts an ISO timestamp or a relative window: 30m, 24h, 7d, 2w.
Development
pip install -e ".[dev]"
pytest -q
The test suite points RUNMETER_DB_PATH at a throwaway file per test, so it never touches a real store.
Design notes
- Tools use consistent
runmeter_prefixes for discoverability. - Read tools carry
readOnlyHint; the single delete tool carriesdestructiveHintand refuses to run without an explicitconfirm, so it cannot wipe the store by accident. - Aggregation runs in Python so multi-tag rows and per-day buckets are handled uniformly, keeping the SQL simple and portable.
- No ORM and one dependency beyond the MCP SDK and Pydantic, by design: low total cost of ownership and easy to audit.
License
MIT. See LICENSE.
Built by Aptica Solutions.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。