GitHub MCP Server
A one-tool MCP server that turns plain-English create_repo commands into GitHub repository create/update calls.
Create a public repository under your account, initialized with a README, with name/description derived from the command.
Replace an existing repository's description.
Replace all topics on a repository (split on spaces/commas and lowercased).
Set a repository's website/homepage URL.
Requires
GITHUB_TOKEN; cannot create private repos or delete anything, and topics must be set in a separate update command.
Provides tools for interacting with GitHub's API, allowing users to create repositories with auto-generated names from descriptions, add topics/tags to repositories, set repository homepages, and initialize repositories with README files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub MCP Server Create a repository for my new React dashboard with tags react typescript ui website https://myapp.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub Meta MCP Server
Create GitHub repositories and edit their description, topics and website from a Claude conversation.
A small Model Context Protocol server with one tool. You (or Claude) pass a plain-English command; the server picks it apart with simple pattern matching and calls the GitHub REST API with your token. There is no language model inside the server, so the wording matters.
Status
Last updated May 2026. Checked in November 2026: npm ci and npm run build succeed, the server starts, and commands in the forms below parse and reach the GitHub API. Calls with a real token were not tested.
Related MCP server: GitHub MCP Server
Tool
create_repo
One argument, command (string). It understands four forms:
Command | What happens |
| Creates a public repo under your account, initialized with a README. The words after |
| Replaces the description. |
| Replaces all topics. Topics are split on spaces or commas and lowercased. |
| Sets the homepage URL. |
Things to know:
Create commands must say
repository, notrepo: "Create a repo called lunchbox" is rejected.Update commands need the repository as
owner/repo, right afterupdate,changeorset.Any command containing
update,changeorsetanywhere, even inside a word such as "dataset", is treated as an update.Set topics with an update command after creating the repo. The server passes topics from a create command to GitHub's create-repository API, which does not accept them.
New repos are always public. There is no option to make them private.
There is no delete.
Install
Build from source with Node 18 or newer:
git clone https://github.com/joewilsonai/github-meta-mcp-server
cd github-meta-mcp-server
npm ci
npm run buildConfigure Claude Desktop
Add this to claude_desktop_config.json, with the absolute path to your clone and your own token:
{
"mcpServers": {
"github-meta": {
"command": "node",
"args": ["/absolute/path/to/github-meta-mcp-server/build/index.js"],
"env": {
"GITHUB_TOKEN": "<your-github-token>"
}
}
}
}Restart Claude Desktop and the create_repo tool appears.
The token is read from the GITHUB_TOKEN environment variable only; the server will not start without it. A classic personal access token with the repo scope (or public_repo, since new repos are public) covers everything the tool does. Create one in GitHub token settings.
Built with
TypeScript, @modelcontextprotocol/sdk 0.6.0 and Octokit.
Available Tools
1 toolcreate_repoC
Create or update GitHub repositories using natural language commands
Inputs: command (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as creating or updating GitHub repositories, making it distinct by default.
The single tool name 'create_repo' follows a clear verb_noun pattern, and since there are no other tools to compare it to, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
A single tool for a GitHub server is too few for the typical scope, which usually involves multiple operations like listing repos, managing issues, or handling pull requests. This feels thin and incomplete for the domain.
The tool surface is severely incomplete for a GitHub server, as it only covers creating or updating repositories. Obvious gaps include retrieving repos, managing issues, pull requests, and other core GitHub functionalities, which will likely cause agent failures.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An MCP server that gives your AI access to the source code and docs of all public github repos
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with GitHub repositories, issues, and pull requests.24 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLM agents to manage GitHub repositories, issues, pull requests, branches, files, and releases through a standardized interface.443 npm8Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform GitHub operations including repository management, file operations, issue tracking, and pull request creation.2-
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-