BugScreen

app.bugscreenPublished by bugscreen.appOfficial publisherv1.0.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

BugScreen lets a coding assistant set up mobile bug reporting and investigate retained bug reports through a hosted remote MCP endpoint.

What you can do
  • Configure mobile bug reporting from the assistant.
  • Investigate retained bug reports that were submitted through BugScreen.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
Consider it when you want an AI coding assistant to help wire up mobile bug reporting in an app, or to look into bug reports already collected in BugScreen.
Requirements
A remote MCP endpoint at the provider's hosted service, reached over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Access is granted through OAuth to a hosted service, so the assistant can reach your BugScreen account data, including retained bug reports. Review what the OAuth grant allows before connecting, and note that report contents are held by the provider.

Installation

In SourceWeft

  1. Open BugScreen in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/app.bugscreen%2Fmcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.