How getsentry/sentry-mcp works
Project type and purpose
• From the file tree we see a pnpm/turbo-powered monorepo hosting several related packages.
• Core packages:
• packages/mcp-server – The core CLI/tooling library with transports (stdio), command definitions, prompts, and internal logic.
• packages/mcp-server-evals – The suite of “eval” functions (autofix, create-project, list-issues, etc.) that implement the CLI’s commands.
• packages/mcp-server-mocks – Test fixtures and mock servers for mcp-server and mcp-server-evals.
• packages/mcp-cloudflare – A full-stack Cloudflare Worker + React/Vite frontend integration for a UI (OAuth, setup guides, Sentry).
• packages/mcp-server-tsconfig – Shared TypeScript configs used across packages.
• This is primarily a developer-tool suite: a CLI with pluggable “eval” modules, local mocks for dev/test, and an optional Cloudflare-hosted UI.
File structure
• Top-level:
• bin/ – Scripts (version bump).
• .github/workflows/ – CI (tests, merges, releases).
• Dockerfile – Containerization.
• turbo.json, pnpm-workspace.yaml – Turbo and pnpm workspace configs.
• packages/mcp-server:
• src/transports/stdio.ts – How the CLI communicates.
• src/toolDefinitions.ts – CLI commands declarative schema.
• src/prompts.ts – Interactive prompts.
• packages/mcp-server-evals:
• src/evals/*.eval.ts – Each file implements one command’s business logic.
• packages/mcp-server-mocks:
• fixtures/ – JSON fixtures of API states.
• index.ts – Mock HTTP/stdio server implementation.
• packages/mcp-cloudflare:
• src/client – React/Vite UI.
• src/server – Worker routes (OAuth, transport layer).
• wrangler.jsonc – Cloudflare Worker config.
• vite.config.ts, tsconfigs – Build and type configs.
README (unavailable)
• No usable content, so we infer from filenames and directory patterns.