
AgentCat
com.agentcatPublished by agentcat.comOfficial publisherv1.0.0Updated Oct 24, 2026
Analytics and debugging for your MCP server — explore usage and sessions, then root-cause errors.
Overview
AgentCat is a remote MCP server that gives an assistant analytics and debugging for your own MCP server, covering usage, sessions and error root-cause analysis.
- What you can do
- Explore usage analytics for your MCP server, such as how it is being used over time and across sessions, and investigate sessions to see what happened in them. Root-cause errors by tracing failures back to their source. The manifest lists no individual tools, so the exact operations are not documented here; the server is reached as a hosted remote endpoint rather than a local package.
- When to use it
- Useful when you operate an MCP server and want an assistant to help you review its usage, inspect sessions, and diagnose errors without switching to a separate dashboard.
- Requirements
- A remote MCP endpoint at the provider's hosted address, reached over streamable HTTP. OAuth authentication is required, so you need an AgentCat account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open AgentCat in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.agentcat%2Fagentcat/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"agentcat": {
"type": "http",
"url": "https://mcp.agentcat.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.