BugScreen MCP Server

by bugscreen Your server? Claim it

answering

BugScreen is answering right now. Last checked 9 min ago.

Configure mobile bug reporting and investigate retained reports with your coding assistant.

Uptime history 12 days of history

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

905 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check BugScreen every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://www.bugscreen.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://www.bugscreen.app/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://www.bugscreen.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://www.bugscreen.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://www.bugscreen.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://www.bugscreen.app/mcp	streamable-http	sign-in	700 ms	9 min ago

Alternatives to BugScreen

same job, measured the same way

VillApps

by villapps

Desktop app with a local MCP server: your coding AI builds business screens, reports and charts.

local only

Ybug

by ybug

Read, filter and triage Ybug website feedback and bug reports from your AI assistant

answering

CARBON

by jarbon

AI testing harness with Jay: risk-based checks, bug investigation, and local evidence reports.

211 installs/wk local only

Top Nutritionist

by coghorizon-nutri

Meal, activity and sleep diary your assistant records into, with reports for your nutritionist

answering

SnagRelay

by snagrelay

Bug reports your coding agent can fix: real element, console errors, failing requests with bodies.

answering

Project Memory MCP

by kaaustubh

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

27 installs/wk local only

Everframe

by everframe

Read in-app bug reports, crashes, screenshots and tickets from mobile, web and TV apps.

answering

Cortex

by danielblomma

Local repo context for coding assistants with semantic search and graph relationships.

91 installs/wk local only

BugScreen — questions

Answers built from our own checks of this server.

Why is there no tool list for BugScreen?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is BugScreen working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 905 ms. The bar chart above shows every period we have measured.

How do I connect BugScreen?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to BugScreen?

No API key is involved. BugScreen answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is BugScreen?

It answers our handshake in 905 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.