issue-tracker

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. This repo dogfoods its own server: use the gh-issues-mcp MCP tools for all issue operations. The gh CLI is not a fallback — treat it as unavailable. If an operation you need isn't covered by any tool below, that's a real gap in the server, not something to route around: say so explicitly, and treat it as a candidate for a new gh-issues-mcp tool (e.g. by filing an issue against this repo) rather than improvising another way to do it.

Conventions

Every tool below (except list_repos) takes an optional repo param, "owner/name", checked against the server's configured repo allowlist. Omit it to target the server's default repo. list_repos() returns the full allowlist plus each repo's effective label vocabulary — call it first when you don't already know the target repo or its vocabulary.

This repo's tracker repo is joachimwedin/gh-issues-mcp (see CLAUDE.md). Pass repo: "joachimwedin/gh-issues-mcp" explicitly on every call rather than omitting it — the server's allowlist also includes other repos, and its configured default may point at one of those instead.

• Discover repos: list_repos() — no params; returns [{ repo, labelVocabulary }] for every repo in the allowlist.
• Create an issue: create_issue(title, body, labels?, repo?) — creates a new top-level issue. If labels is given, only labels in the resolved repo's configured vocabulary are accepted — see docs/agents/triage-labels.md.
• Read an issue: view_issue(number, repo?) — returns body, labels, full comment history, the issue's parent (if any, else null), and its sub-issues (if any, else []) in one call.
• List issues: list_issues(state?, labels?, repo?) — PRs are excluded automatically, since this server treats issues, not PRs, as the triage surface.
• Comment on an issue: comment_issue(number, body, repo?).
• Apply / remove labels: edit_labels(number, add?, remove?, repo?). Only labels in the resolved repo's configured vocabulary are accepted — see docs/agents/triage-labels.md. If a label you need isn't in the vocabulary, flag it as a gap (config or tool) rather than trying to force it another way. Unlike the other tools, its result is { repo, labels } (the resolved repo and the issue's resulting label list), not a tagged issue object.
• Close: close_issue(number, comment, repo?) — comment is required, so an issue can never be closed without an explanation.
• Create a sub-issue: create_sub_issue(parent_number, title, body, repo?) — creates a new issue and links it to the parent via GitHub's sub-issues API in one call. Parent and child are always in the same repo.
• Edit an issue: edit_issue(number, title?, body?, repo?) — updates an existing issue's title and/or body. At least one of title/body must be given.