Trace AI agent execution: every tool call, every error, every dollar. Open source, local-first.
MCPpedia last refreshed this data
io.github.KryptosAI/agent-observability is an MCP server that trace AI agent execution: every tool call, every error, every dollar. Open source, local-first. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 57/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"agent-obs": {
"args": [
"-y",
"agent-obs@latest",
"server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Open source agent observability — see what your agents did, why they failed, and what it cost. Runs locally. No cloud required.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'agent-obs' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked agent-obs against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / analytics
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
The official MCP server implementation for the Perplexity API Platform
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
MCP Security Weekly
Get CVE alerts and security updates for io.github.KryptosAI/agent-observability and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Open source agent observability — see what your agents did, why they failed, and what it cost. Runs locally. No cloud required.
One command. No manual config. No copy-paste.
npx agent-obs@latest setup
This auto-detects your AI agent (opencode, Claude Code, Cursor) and configures everything:
Then restart your agent. Every action will now self-report.
agent-obs dashboard # http://localhost:9400 — see your sessions appear
After running a task in your agent, the dashboard shows:
setup can't detect your agent)opencode: Add to opencode.json:
{
"mcp": {
"agent-obs": {
"command": "npx",
"args": ["-y", "agent-obs@latest", "server"],
"enabled": true
}
}
}
Claude Code: Create .mcp.json:
{
"mcpServers": {
"agent-obs": {
"command": "npx",
"args": ["-y", "agent-obs@latest", "server"]
}
}
}
Cursor: Add to Cursor Settings > MCP:
{
"mcpServers": {
"agent-obs": {
"command": "npx",
"args": ["-y", "agent-obs@latest", "server"]
}
}
}
See Agent-Specific Setup below for detailed per-platform instructions including self-reporting directives.
Note: All data is written to a local SQLite database in
~/.agent-observability/. No data leaves your machine.
For agents that can't self-report, wrap any MCP server and every tool invocation gets traced automatically:
agent-obs proxy --desc "fix login bug" -- npx @modelcontextprotocol/server-filesystem /tmp
Proxy mode captures only MCP tool calls (~30% of typical agent actions). Prefer the setup / MCP server approach above.
.mcp.json in your project root:{
"mcpServers": {
"agent-obs": {
"command": "npx",
"args": ["-y", "agent-obs@latest", "server"]
}
}
}
.claude/instructions.md (or reference the existing SKILL.md under .claude/skills/agent-obs/SKILL.md):After every tool call, report to agent-obs's log_tool_call.
Start each task with start_session. End with end_session.
agent-obs dashboard, open http://localhost:9400, and look for your session after the agent completes a task.~/.cursor/mcp.json, or Settings → MCP → Add new global MCP server):{
"mcpServers": {
"agent-obs": {
"command": "npx",
"args": ["-y", "agent-obs@latest", "server"]
}
}
}
.cursorrules (or .cursor/rules/agent-obs.md):After every tool call, you MUST call the agent-obs MCP server's log_tool_call tool.
Include toolName, status (success/error), outputSummary, and durationMs.
Start each session with start_session and end with end_session.
agent-obs dashboard, open http://localhost:9400, and look for your session after the agent completes a task. ┌──────────────────────────┐
│ agent-obs server │
│ (self-reporting) │
│
... [View full README on GitHub](https://github.com/kryptosai/agent-observability#readme)