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.