About issuewatcher
Ranks new GitHub issues for your AI assistant: what to pick up, what may break your projects
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y issuewatcher-mcpGITHUB_TOKENSecretA GitHub personal access token with read-only access. Create one at https://github.com/settings/personal-access-tokens/newSCORING_MODEcontributor (issues you could pick up), consumer (issues that may break your projects) or both.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 4d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| mode | enum | No | contributor: what could I pick up and fix (good first issues, unassigned, fresh). consumer: what could break my projects (issues in libraries I depend on). both: a mix of the two.contributor | consumer | both |
| limit | integer | No | How many issues to return (1-25). |
| repos | array | No | Optional: only these repos, each as owner/name. |
| since | string | No | How far back to look, as a number plus h or d, for example 24h, 3d or 7d. Maximum 30d. |
| source | enum | No | Which watched repos to look at: repos the user starred, source repos of libraries their projects use, or both.starred | dependencies | both |
| min_score | integer | No | Only return issues scoring at least this (0-100). |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.