GitHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | A GitHub personal access token with repository creation permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_repoC | Create or update GitHub repositories using natural language commands |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.