create-issueLABSCO 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:5173before 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 — git clone https://github.com/ualUsham/mcp-github.git
USE CASES
01
Filing an issue without leaving the conversation
Describe the bug in a sentence, let the description prompt draft the body, then open it against the repository.
02
Seeing what is already reported
List the repository's open issues before you file, so you find the duplicate rather than create it.
03
Finding a library that does the thing
Use the query prompt to turn a rough description into a GitHub search, then run it and read the results.
04
Writing a pull request description
Use the PR description prompt when you have the changes but not the words for them.
4 tools
Listed in project docs. Your client may show a different list.
get-repo-infolist-issuessearch-reposBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- node on PATH
- GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/ualUsham/mcp-github.git
cd mcp-github
npm install
npx tscMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"gh": {
"command": "node",
"args": [
"<YOUR_PATH_TO_INDEX_JS_FILE>"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}<YOUR_PATH_TO_INDEX_JS_FILE> is the full path to build/index.js inside your clone; npx tsc creates that file.
