xenia
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@xeniashow me failures in the last 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
xenia
A local MCP and tray icon for keeping track of how well agents are acheiving their goals, and what is going wrong. Install and run on linux or mac with
./bin/xeniaNeeds Python 3.11+
MCP tools
xenia_report
| One row is |
| What an agent set out to do, in its own words, and whether it got there. The label comes from its plan where it kept one and the outcome is read off the calls made under it. |
| Something the user asked for, and how it turned out. |
| A kind of work that has failed more than once, worst first, grouped across sessions and repos. |
| Work a session did again soon after it had already attempted the same thing. |
| Counts, failure rates, latency and reply size, per tool, broker, channel, host, repo or signature. |
| What was written, how often each file was rewritten, and how much of that hashed to what was already there. |
xenia_calls
One row of any of the above, broken into the individual calls behind it.
xenia_trace
The actions between an action_id failure and the fix.
Arguments
since (24h, 7d, or a date), repo — work outside any checkout is filed under general — and limit apply to every view. Where tool, via, channel, session and signature are accepted they match exactly or as a glob, so one via: "acme-*" covers every call through a site's brokers, and a signature from any view drills straight into the calls behind that row.
See ARCHITECTURE.md.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceProvides observability for multi-agent workflows by tracking hierarchical task structure, architectural decisions, reasoning, encountered problems, code modifications with Git diffs, and temporal metrics.Last updated49
- AlicenseBqualityDmaintenanceEnables AI assistants to query and analyze AI agent sessions from observability providers like Shepherd (AIOBS) and Langfuse, allowing users to debug agent runs, compare sessions, track performance, and analyze LLM usage patterns.Last updated18MIT
- Alicense-qualityFmaintenanceEnables comprehensive collection and analysis of ClaudeCode development sessions, including agent tracking, tool usage analytics, and performance metrics.Last updatedMIT
- Alicense-qualityDmaintenanceTracks and analyzes AI agent tool calls with event logging, dashboard, per-tool and per-agent analytics, and error monitoring.Last updatedMIT
Related MCP Connectors
AI agent run monitoring with incident replay and SLA receipts.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
Runtime permission, approval, and audit layer for AI agent tool execution.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iondrive-co/xenia'
If you have feedback or need assistance with the MCP directory API, please join our Discord server