create_github_repositoryLABSCO SUMMARY
A new repository exists by the time you finish describing it.
It does exactly two things, which keeps the scope of the token you hand over legible — creating the repository with its visibility and README settled in the same breath as the idea for it.
What it is
Two GitHub operations exposed as tools: creating a repository and deleting one. It is a small Python server that authenticates with a personal access token read from a local .env file.
What you get
- A repository created by name, set public or private, with a description and a README initialized by default
- A repository deleted by name
- Credentials kept out of the client configuration — the token is read from a .env file beside the server
Requirements
Python 3 with the listed dependencies, and a GitHub personal access token carrying repo permissions, placed in a .env file. Deletion through the GitHub API is permanent, so the token you give it decides how much can be removed.
Setup effort
Build from source
USE CASES
01
Starting a project the moment you decide on it
Create the repository by name with its description and visibility set, initialized with a README, without opening GitHub.
02
Spinning up a private scratch repository
Create it private for an experiment, so throwaway work still gets version control without becoming public by accident.
03
Cleaning up experiments that went nowhere
Delete the repository by name when it has served its purpose — permanently, so be sure it is the one you meant.
04
Setting up several repositories in one sitting
Create them one after another in the same conversation, each with its own visibility and description, rather than repeating a web form.
2 tools
Listed in project docs. Your client may show a different list.
delete_github_repositoryBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Python 3
- GITHUB_TOKEN (a token with repo permissions) in a .env file next to simple_mcp_server.py
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/amanueltefera843110/MCP-Repo-Manager-
cd MCP-Repo-Manager-
pip install -r requirements.txtGenerate a GitHub token with "repo" permissions at https://github.com/settings/tokens
Create a .env file in the same directory as simple_mcp_server.py containing GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github-repo-creator": {
"command": "python3",
"args": [
"<YOUR_PATH_TO_SIMPLE_MCP_SERVER>"
],
"env": {}
}
}
}The configuration on this page does not set GITHUB_TOKEN; the project's instructions put it in a .env file. To supply GITHUB_TOKEN without depending on where the server looks for that file, use the block's "env" section.
