git-telemetry-mcp

# Git Telemetry MCP An MCP server implementing the documented, focused subset of the MCP `2026-07-28` protocol. It provides a **Development Time Machine** by analyzing git reflogs, commit history, working directory deltas, and permitted shell history to give AI assistants temporal context. ## Quick Start ```bash # Install dependencies uv sync # Run the MCP server (HTTP JSON-RPC on http://127.0.0.1:8787/mcp, SSE on /sse) uv run git-telemetry-mcp # Run tests uv run pytest ``` ## MCP Client Configuration Add to your MCP client config (e.g. Claude Desktop, Cursor, OpenCode): ```json { "mcpServers": { "git-telemetry": { "url": "http://127.0.0.1:8787/mcp" } } } ``` ## HTTP security boundaries The HTTP JSON-RPC endpoint is `POST /mcp`; the server also exposes the SSE stream at `GET /sse`. Set `GIT_TELEMETRY_AUTH_TOKEN` to require `Authorization: Bearer <token>` on every HTTP/SSE request. When the variable is unset, the server remains usable for local development but accepts requests only from loopback clients and localhost origins. Requests must use `Content-Type: application/json`, are size-bounded, and reject non-local origins by default. Configure `GIT_TELEMETRY_ALLOWED_ROOTS` (path-separated) to restrict repository arguments to approved roots. ### Protocol scope The server implements `initialize`, `notifications/initialized`, `tools/list`, `tools/call`, `resources/list`, `resources/read`, `prompts/list`, and `prompts/get` over its HTTP JSON-RPC and SSE transports. Unsupported MCP methods return JSON-RPC `-32601` (`Method not found`); this implementation does not claim support for completion, sampling, logging, subscriptions, or other methods not listed above. HTTP requests are stateless; SSE uses a bounded, in-memory queue and is not a durable session store. ### Shell-history boundaries `dev_activity` does not read arbitrary paths. An explicit `shell_history_path` must be a regular file beneath a directory listed in `GIT_TELEMETRY_ALLOW…