GitHub Integrated MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_OWNER | No | Your GitHub username | |
| GITHUB_TOKEN | Yes | GitHub Personal Access Token for API authentication | |
| GITHUB_DEFAULT_REPO | No | Your default repository name |
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 |
|---|---|
| echoC | Echo back the input |
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 between tools, making disambiguation perfect. The tool 'echo' has a clear and distinct purpose that cannot be confused with any other tool in this set.
With a single tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'echo' follows a simple verb pattern, and there are no inconsistencies in naming conventions to evaluate.
A single tool is generally too few for a server named 'GitHub Integrated MCP Server', which suggests a broader scope related to GitHub operations. This minimal tool set does not align well with the implied domain, indicating a significant mismatch in scope.
The tool set is severely incomplete for the server's implied purpose of GitHub integration. With only an 'echo' tool, there are no operations for repositories, issues, pull requests, or any other GitHub-related functionalities, leaving major gaps that will cause agent failures.