agentic-observability-mcp
Provides unified AI agent observability including tracing, cost tracking, performance monitoring, anomaly detection, and audit trails via MCP.
README
agentic-observability-mcp
AI agent observability for MCP. Tracing, cost tracking, performance monitoring, anomaly detection, and audit trails — all via Model Context Protocol.
Why This Exists
AI agents burn tokens, call tools, make decisions, and sometimes get stuck in loops. You need to know what they're doing, what it costs, and when something goes wrong. No existing MCP server provides unified agent observability. This one does.
Track every LLM call, every tool invocation, every decision — with automatic cost calculation and anomaly detection.
What It Does
Tracing
trace_agent_action— Log any agent action (tool calls, LLM requests, decisions, errors) with metadata and timestamps
Cost Tracking
track_token_usage— Track token usage per LLM call with automatic cost calculation from built-in pricing tables (Claude, GPT, Gemini, Mistral)get_cost_report— Aggregate cost breakdown across sessions, grouped by model, provider, tool, or session
Performance Monitoring
log_tool_call— Log MCP tool calls with latency, success/failure, and error detailsget_session_summary— Full session report: cost, tokens, tool stats, error count, model breakdown, duration
Anomaly Detection
detect_anomaly— Flag unusual patterns:- cost_spike — Session or single-call cost exceeds thresholds
- error_rate — Tool failure rate above 30%
- latency_spike — Tool calls exceeding 10s
- loop_detection — Same tool called with same params 3+ times (agent stuck)
- token_explosion — Single call or session using excessive tokens
Resources (Static Knowledge)
observability://pricing— Current LLM pricing table (per-token costs for all major models)observability://best-practices— Agent observability best practices guide
Installation
Claude Desktop / Claude Code
Add to your MCP configuration (~/.claude/settings.json or project .mcp.json):
{
"mcpServers": {
"agent-observability": {
"command": "npx",
"args": ["agentic-observability-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"agent-observability": {
"command": "npx",
"args": ["agentic-observability-mcp"]
}
}
}
Windsurf / VS Code
Same pattern — add the server to your MCP configuration file.
Use Cases
For agent framework developers:
Instrument your agent loop with track_token_usage and log_tool_call to get real-time cost and performance data without building your own telemetry.
For teams running agents in production:
Use detect_anomaly to catch stuck agents (loop detection), runaway costs (cost spike), and degraded tool performance (latency spike) before they become incidents.
For cost optimization:
Use get_cost_report grouped by model to identify which models are eating your budget. Switch expensive reasoning calls to cheaper models where quality allows.
For compliance and audit:
Every trace_agent_action with type "decision" creates an audit record. Include reasoning in the description for full traceability.
Example
Agent: "Track that I just used 1,500 input tokens and 800 output tokens
with claude-sonnet-4 on Anthropic for session agent_run_001"
--> Returns:
{
"call_cost": 0.016500,
"running_session_total": 0.016500,
"model": "claude-sonnet-4",
"provider": "anthropic",
"pricing_used": { "input": 0.000003, "output": 0.000015 },
"model_breakdown": {
"claude-sonnet-4": {
"calls": 1,
"input_tokens": 1500,
"output_tokens": 800,
"cost": 0.016500
}
}
}
Agent: "Check session agent_run_001 for anomalies — cost spike and loop detection"
--> Returns:
{
"anomalies_found": 0,
"anomalies": [],
"checks_performed": ["cost_spike", "loop_detection"]
}
Built-in Pricing Table
Automatically calculates costs for these models (override with custom pricing if needed):
| Provider | Models |
|---|---|
| Anthropic | Claude Opus 4, Sonnet 4, Haiku 4, 3.5 Sonnet, 3.5 Haiku, 3 Opus |
| OpenAI | GPT-4o, GPT-4o Mini, GPT-4 Turbo, o1, o1-mini, o3-mini |
| Gemini 2.5 Pro, 2.5 Flash, 2.0 Flash, 1.5 Pro | |
| Mistral | Large, Medium, Small, Codestral |
| Local | Zero cost (self-hosted models) |
Pricing
| Tier | Price | Agents | Retention | Events/Month |
|---|---|---|---|---|
| Free | $0 | 1 | 7 days | 10,000 |
| Starter | $59/month | 5 | 30 days | 100,000 |
| Pro | $299/month | 25 | 90 days | 1,000,000 |
| Enterprise | $999/month | Unlimited | 1 year | Unlimited + SOC2 reporting |
Architecture
v1 uses in-memory storage (Maps). Data is lost on server restart. The storage layer (src/storage.js) is structured for easy swap to Redis or Postgres in v2.
Requirements
- Node.js 18+
- No API keys needed
- No external dependencies beyond MCP SDK and Zod
License
MIT
Keywords
mcp, mcp-server, observability, agent-tracing, cost-tracking, token-usage, ai-agent, performance-monitoring, audit-trail, model-context-protocol
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。