Universal GitHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPOS | No | JSON array of repository configurations (optional). If not provided, example configuration is used. | |
| GITHUB_TOKEN | Yes | Your GitHub personal access token with repo 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wpcliD | WordPress CLI tool for CreatorLMS |
| githubC | GitHub API integration - pure remote operations for repositories: example-repo |
| docsC | Company documentation and best practices - enforces rules for development |
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 3 tools
The three tools are distinct in their domains: WordPress CLI, GitHub API, and documentation. There is no overlap between them, so an agent is unlikely to confuse one for another, though the GitHub tool is broadly scoped.
All tool names are lowercase single nouns, but they do not follow a verb-noun or consistent action-based pattern. 'wpcli' is a compound name, 'github' is a platform name, and 'docs' is an abbreviation, which feels ad hoc rather than systematic.
Three tools is within the acceptable range and not excessive. However, the server is named 'Universal GitHub MCP Server' yet includes a WordPress tool and a docs tool, making the count feel both under-scoped for GitHub and over-inclusive for the stated purpose.
For a GitHub-oriented server, there is only one vague 'github' tool with no explicit CRUD or workflow operations visible. The other two tools address unrelated domains, leaving major gaps in GitHub functionality that would likely cause agent failures.