Summary

The prompts are why this is more than four API calls.

Four tools over the GitHub API is a small thing on its own. What makes it usable is that the prompts sit in the client's integration menu — pick the issue-description prompt, describe the bug in a sentence, and the text that goes into the tool call is already written. The response-formatting prompt does the same on the way back, turning raw API JSON into something a person reads. Scope is genuinely small: issues, repo info and search, no pull requests or code.

What it is

A small TypeScript MCP server over the GitHub API, built on Octokit. It covers four operations and pairs them with five prompts, which is the part that distinguishes it: the prompts turn a rough intent into the description or the search query that the tools then act on.

What you get

A repository's details, its issues listed, and a new issue opened — `get-repo-info`, `list-issues`, `create-issue`
Repository search across GitHub — `search-repos`
Five prompts that do the writing: an issue description, a pull request description, a search query, the parameters for creating an issue, and a pass that formats raw GitHub API output into something readable — `create-issue-description`, `create-pull-request-description`, `search-repos-prompt`, `create-issue-prompt`, `enhance-github-response`
MCP Inspector wiring documented, so you can exercise the tools at `http://localhost:5173` before pointing a client at them

Requirements

A GitHub personal access token, passed as `GITHUB_TOKEN`. There is no published package: clone, `npm install`, compile with `npx tsc`, and point your client at `build/index.js` by absolute path. A `.env.example` in the repository shows the variables to set. The token's scopes decide what it can do — issue creation needs write access to the repository you aim it at.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary