René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add support for resolving/unresolving PR review threads","articleBody":"### Describe the feature or problem you'd like to solve\n\nWhen working with PR review comments via MCP, there's no way to resolve or unresolve review threads programmatically. The `get_review_comments` method returns `IsResolved` status (related to #1086), but there's no corresponding mutation to change it.\n\nCurrently, to resolve review threads, users must manually go to the GitHub UI and click \"Resolve conversation\" for each thread.\n\n### Proposed solution\n\nAdd a new tool `resolve_review_thread` (or extend existing PR review tools) that wraps the GraphQL mutation:\n\n```graphql\nmutation {\n  resolveReviewThread(input: {threadId: \"PRRT_xxx\"}) {\n    thread { isResolved }\n  }\n}\n```\n\nAnd optionally `unresolveReviewThread` for the reverse operation.\n\n**Suggested tool schema:**\n```json\n{\n  \"name\": \"resolve_review_thread\",\n  \"description\": \"Resolve or unresolve a PR review thread\",\n  \"inputSchema\": {\n    \"type\": \"object\",\n    \"properties\": {\n      \"thread_id\": {\n        \"type\": \"string\",\n        \"description\": \"The node ID of the review thread (e.g., PRRT_kwDO...)\"\n      },\n      \"resolve\": {\n        \"type\": \"boolean\",\n        \"description\": \"true to resolve, false to unresolve\",\n        \"default\": true\n      }\n    },\n    \"required\": [\"thread_id\"]\n  }\n}\n```\n\n### How will it benefit GitHub MCP Server and its users?\n\n- **AI agents can complete PR review workflows end-to-end** — after addressing review feedback, the agent can mark threads as resolved\n- **Batch operations become possible** — resolve multiple threads programmatically instead of manual UI clicks\n- **Better integration with automated code review tools** — bots like Copilot PR reviewer leave comments that could be auto-resolved once addressed\n\n### Use case\n\n1. AI agent reads PR review comments via `get_review_comments`\n2. Agent addresses the feedback (makes code changes)\n3. Agent resolves the addressed threads ← **not currently possible**\n\n### Additional context\n\nThe thread IDs are already returned by `get_review_comments` in the `ID` field (e.g., `PRRT_kwDOE5NpvM5okADy`), so no additional API calls would be needed to obtain them.","author":{"url":"https://github.com/kulakowka","@type":"Person","name":"kulakowka"},"datePublished":"2026-01-08T17:31:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/1768/github-mcp-server/issues/1768"}