Prwatch

Name: Prwatch
Author: CloudCorpRecords

by CloudCorpRecordsversion 0.2.0i★ –iRuns on your computer

Registry nameio.github.CloudCorpRecords/prwatch

Install

Overview

Description from the maker (original English)

Attention report for your open GitHub PRs: what needs you right now.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "prwatch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/prwatch",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add prwatch -- npx -y @reneturcios/prwatch mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "prwatch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/prwatch",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "prwatch": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/prwatch",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1387 servers in this category
Published to the registry more recently than 88% of the other 1387 servers in this category
Basic checks equal to or better than 100% of the other 1387 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Prwatch safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

prwatch

What needs your attention right now? prwatch answers that question for contributors with open PRs.

It was born from a real day: three PRs open in one repo, CodeRabbit reviews on all three, a Vercel deploy failure that was not the author's fault, and no way to see at a glance which PR actually needed work. Manually reading every review thread on every PR is the old way. prwatch ranks your open PRs by urgency with human readable reasons, so you open the right one first.

Quickstart

npx @reneturcios/prwatch attention

Install

Requirements: Node 20+.

npx @reneturcios/prwatch attention

Or install it globally:

npm install -g @reneturcios/prwatch

Set GITHUB_TOKEN (or GH_TOKEN) for the 5000 req/hr authenticated rate limit. Without a token it works at the 60 req/hr unauthenticated rate.

Run it with Docker

prwatch also ships as a container image on GHCR: ghcr.io/cloudcorprecords/prwatch.

Use it as a stdio MCP server:

docker run -i ghcr.io/cloudcorprecords/prwatch

Any CLI command can be passed after the image name instead of the default mcp argument:

docker run ghcr.io/cloudcorprecords/prwatch <command> [args]

Authentication

A token is optional. --repo mode and prwatch show work without one, since they never touch the search API. Account-wide reports (attention / list without --repo) use author: search, which GitHub restricts for unauthenticated callers on some accounts, so a token is recommended there. A classic token with no scopes is enough for public data; without one you get clear guidance instead of a raw 422.

CLI usage

prwatch attention                     # rank my open PRs by urgency

prwatch attention --user octocat --repo shadcn-labs/pdfcn prwatch attention --json # machine readable output prwatch list # simple one line per PR prwatch show https://github.com/shadcn-labs/pdfcn/pull/92

Example output:

[ACTION]  74  shadcn-labs/pdfcn#92

feat: add Business Letter block

4 unresolved review threads need a reply or code change (business-letter.tsx, business-letter.mdx) https://github.com/shadcn-labs/pdfcn/pull/92

[READY] 45 shadcn-labs/pdfcn#93 feat: add Resume block

Approved and green, ready to merge. https://github.com/shadcn-labs/pdfcn/pull/93

prwatch show gives the deep dive: review state, every check with its conclusion, unresolved review threads with file and line, and the full attention breakdown.

MCP server

Same engine as the CLI, exposed over stdio for Claude, Cursor, and Cline:

Tool	What it does
`attention_report({user?, repo?})`	Ranked attention report with scores, categories, and reasons
`list_my_prs({user?, repo?})`	Simple list of open PRs
`pr_status({url})`	Deep dive on one PR: reviews, checks, threads, attention score

Claude Code / Cursor config (~/.claude.json or MCP settings):

"mcpServers": { "prwatch": { "command": "node", "args": ["/absolute/path/to/prwatch/dist/mcp.js"], "env": { "GITHUB_TOKEN": "ghp_your_token_here" } } } }

Start it directly with npm run start:mcp.

How scoring works

Every open PR starts at 50 points and gains or loses urgency from signals:

Signal	Effect
Changes requested by a reviewer	+30, category ACTION
Merge conflict (unmergeable branch)	+25, category ACTION
Failing check on your code (build, test, lint, DCO)	+12 each, category ACTION
Unresolved review thread that asks for a change	+8 each, category ACTION
Approved, checks green, mergeable	READY, score capped at 45
Failing check that is not your fault (for example Vercel "Authorization required to deploy")	classified BLOCKED_EXTERNAL, low urgency
Check suite waiting for a maintainer to approve the workflow run (`action_required`, the usual fork PR state)	classified BLOCKED_EXTERNAL, low urgency; the check never ran, so it is never counted as a failing check
Checks still running	WAITING
7+ days of silence with no approval	STALE

Score is clamped to 0-100. Categories rank in this order: ACTION, BLOCKED_EXTERNAL, READY, WAITING, STALE. The report sorts by score, then category.

Two judgment calls worth knowing:

External blockers are not failures. A preview deploy that fails because a maintainer has to authorize it is GitHub-marked "failure", but no code change fixes it. prwatch detects known patterns (authorization required, sign in to deploy, waiting on team approval) and files them as external, so they never inflate your urgency. The same applies to a check run that concluded action_required: GitHub held the workflow for maintainer approval (the normal state of a fork PR), so the check never ran and carries no failure evidence at all, whatever its name or description says.
Thread resolution is approximated. The GitHub REST API cannot say whether a review thread is resolved, so top level review comments from non authors count as open threads. Comments that suggest a change (code suggestions, "please", "consider", "fix") count as actionable.

Development

npm install

npm test # tsx --test test/*.test.ts npm run build # tsc, emits to dist/ npm run dev # run the CLI from source

Fixtures in test/fixtures/ are modeled on the real shapes of shadcn-labs/pdfcn PRs #92, #93, and #94 from 2026-10-13. Tests never touch the network.

License

The toolkit

This tool is one of four in a lifecycle for open-source contribution work, all published under the @reneturcios npm scope and each available as a CLI and an MCP server ( mcp):

gatefile (npx @reneturcios/gatefile) extracts a repo's contribution gates into a committed contribution-gates.json.
greenlight (npx @reneturcios/greenlight) pre-flights issues (GO / RISKY / TAKEN / GATED / STALE), consumes gatefile's output in check and scan, then claims, preps, and opens PRs.
claimcheck (npx @reneturcios/claimcheck) watches for stale claims and fixes parked on forks.
prwatch (npx @reneturcios/prwatch) triages your open PRs by what needs you right now.

If prwatch saved you time, star this repo: it helps other developers find it.

Prwatch

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

prwatch

Quickstart

Install

Run it with Docker

Authentication

CLI usage

MCP server

How scoring works

Development

License

The toolkit