Patchrooms

io.github.liknenSPublished by GitHub account liknenSv1.0.0Updated Oct 28, 2026

Agent-ready feedback for AI-built apps — read and close UI feedback reports over MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Patchrooms gives an assistant OAuth-secured access to UI feedback reports from AI-built apps, so it can read and close them over MCP.

What you can do
  • Read UI feedback reports collected from AI-built apps.
  • Close feedback reports once they are addressed.
  • Work against a Patchrooms project through a hosted remote endpoint rather than a local install.
When to use it
Useful when a team collects UI feedback on an AI-built app in Patchrooms and wants the assistant to review open reports and mark them resolved without switching tools.
Requirements
A remote MCP endpoint at room.patchrooms.com over streamable HTTP. OAuth authentication is required, with an Authorization header carrying a Bearer pr_sk_ API key that has the feedback:read scope; the key is created in Patchrooms project settings. No local package or environment variables are needed.
Before you install
The server requires an API key sent in the Authorization header, so treat it as a secret and grant only the scopes needed. Closing reports changes project data, so confirm before letting the assistant resolve feedback. Feedback content is sent to the hosted Patchrooms service.

Installation

In SourceWeft

  1. Open Patchrooms 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/io.github.liknenS%2Fpatchrooms/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": {
    "patchrooms": {
      "type": "http",
      "url": "https://room.patchrooms.com/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.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.