LLM Pulse MCP Serverofficial
A
licenseA
qualityB
maintenanceMonitors brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.
Last updated
1
MIT
gitwhy-mcp
Server Details
The shared AI context engine for git — save, search, and share the reasoning behind code changes. Captures the why behind every commit and slide on PRs for coding agents.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.2/5 across 8 of 8 tools scored.
Server CoherenceA
Disambiguation4/5
Most tools have distinct purposes, such as gitwhy_get for retrieval, gitwhy_save for creation, and gitwhy_publish for sharing. However, gitwhy_list and gitwhy_status overlap in functionality, as both can list contexts or check status, which might cause confusion for an agent. The descriptions help clarify, but the overlap is noticeable.
Naming Consistency5/5
All tool names follow a consistent gitwhy_verb pattern, such as gitwhy_get, gitwhy_list, and gitwhy_save. This uniformity makes it easy for an agent to predict and understand the tool set, with no deviations in naming conventions.
Tool Count5/5
With 8 tools, the count is well-scoped for managing development contexts in a Git repository. Each tool serves a specific role in the lifecycle, from saving and searching to publishing and syncing, without feeling excessive or insufficient for the domain.
Completeness5/5
The tool set provides comprehensive coverage for the GitWhy domain, including CRUD operations (save, get, list, search), lifecycle management (sync, publish), and integration features (post_pr, status). There are no obvious gaps, as all core workflows for context management are supported.
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!
Related MCP Servers
- Alicense-qualityAmaintenanceProvides regulatory and compliance intelligence from free government sources, including rules, recalls, enforcement actions, and comment deadlines, classified by industry and severity.Last updatedMIT
- AlicenseAqualityAmaintenanceCompetitive intelligence platform with 24 tools. Monitor competitor pricing, content, positioning, tech stacks, and AI visibility — track how ChatGPT, Claude, and Gemini rank your brand.Last updated332MIT
- Flicense-qualityCmaintenanceEnables users to monitor and analyze competitor LinkedIn posts, extract insights, generate original post concepts, and create graphics-ready content with metadata.Last updated