Ybug

What Ybug MCP server does

The Ybug MCP server exposes Ybug feedback and bug reports to compatible MCP clients. Ybug reports can include a screenshot, page URL, browser, device, screen size, and optional console logs or network requests. An assistant can use the server to review that information, group or filter reports, inspect individual issues, and support triage workflows.

Read access covers projects, project configuration data, team tags, assignable members, feedback records, report comments, console logs, and network requests. Triage actions are available on plans that include the required features: assistants can change a report’s status, priority, type, assignee, or tags; add an internal comment; and create a tag.

How it works

Ybug hosts the service remotely at https://mcp.ybug.io/mcp, so the repository does not contain a server that users install or run locally. The endpoint uses streamable HTTP. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, and the client prompts the user to sign in with a Ybug account, choose a team, and approve access.

The server acts within the signed-in user’s permissions and a single selected team. It can access only projects available to that user and can change only data that user could change in the Ybug dashboard. Report text comes from external reporters and may contain instructions; coding agents should have their proposed actions reviewed before approval.

Setup and configuration

Add https://mcp.ybug.io/mcp as a remote MCP server in the chosen client, then complete the Ybug sign-in and team approval flow. No API key is required. For Claude Code, the documented command is:

claude mcp add --transport http ybug https://mcp.ybug.io/mcp

Client-specific setup documentation is provided for Claude web and desktop, ChatGPT, Codex, Claude Code, Cursor, and VS Code. Other clients need support for the server’s remote streamable HTTP transport and OAuth flow.

Tools and capabilities

The Ybug MCP server provides these tools:

• list_projects lists accessible projects.
• get_project returns a project’s statuses, priorities, and feedback types.
• list_tags lists team tags.
• list_project_members lists people who can receive assignments.
• list_feedback searches reports by status, priority, type, tags, assignee, date, or keyword.
• get_feedback reads a report with screenshot and video links.
• get_feedback_console_logs and get_feedback_network_requests retrieve diagnostic data.
• list_comments reads report comments.
• update_feedback changes supported triage fields.
• add_comment adds an internal comment.
• create_tag creates a team tag.

Limitations and notes

Read tools are included with the BASIC plan, while triage tools require STARTUP or a higher plan. MCP access is not available on FREE, and there is no additional MCP charge. The assistant cannot delete records, change settings, or send public comments.

Reporter and commenter contact details, widget-provided user data, and reporter location are not sent to the assistant. Screenshot and video links expire after approximately one hour. Moving a report to Resolved or Closed may send an automatic reply to the reporter if that feature is enabled in Ybug. Access can be revoked from Ybug’s Connected apps settings.