Github
Server Details
GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-github
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 38 of 38 tools scored.
Most tools target distinct purposes (e.g., ask_pipeworx vs. get_repo vs. validate_claim), but there is some overlap between ask_pipeworx and ask_pipeworx_grounded, and between bet_research and polymarket_edges. Overall, an agent can generally distinguish them.
Tool names lack a consistent pattern: some are verb_noun (search_repos, get_user), others are noun_verb (entity_profile), and many are compound descriptor phrases (polymarket_arbitrage, scan_dependency). This mixed convention makes the set feel disjointed.
38 tools is excessive for a server named 'Github', especially since many tools (e.g., ai_visibility_check, bet_research) are unrelated to GitHub functionality. The count would be appropriate for a broader 'Pipeworx' server but not for a focused GitHub server.
The GitHub-relevant tools are limited to read-only operations (get_repo, list_commits, etc.), lacking essential actions like creating/updating repos, issues, or pull requests. The inclusion of numerous non-GitHub tools does not compensate for these gaps.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!