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.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 8 tools
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
gitwhy_getgitwhy_listgitwhy_post_prgitwhy_publishgitwhy_savegitwhy_searchgitwhy_statusgitwhy_sync
Add one secure layer between your agents and this server.