BugTape
ai.bugtapePublished by bugtape.aiOfficial publisherv1.0.0Updated Oct 24, 2026
Production bugs with replay, network, console and stack, ranked for your coding agent to fix.
Overview
Gives an assistant ranked production bug reports with replay, network, console and stack details so it can work on fixes.
- What you can do
- BugTape is a remote MCP server that supplies production bug information to a coding agent. According to the registry description, each bug includes replay, network, console and stack data, and the bugs are ranked so the agent can prioritize which to fix. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when an assistant is expected to triage or fix production issues and needs the surrounding replay, network, console and stack context in one place. Less useful for projects without production bug reports or for agents that only work on local code.
- Requirements
- A remote MCP endpoint at over streamable HTTP. No packages, environment variables or headers are declared, and no authentication is declared. Network access to the endpoint is required.
Installation
In SourceWeft
- Open BugTape 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/ai.bugtape%2Fbugtape/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": {
"bugtape": {
"type": "http",
"url": "https://app.bugtape.ai/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 10, 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.