@extn/segi-mcp-nestjs

Model Context Protocol server that walks an AI coding agent (Claude Code, Cursor, etc.) through wiring @extn/segi-nestjs into a NestJS project.

Connect (Claude Code)

claude mcp add segi-nestjs -- npx -y @extn/segi-mcp-nestjs

Then ask the agent something like "Add segi error monitoring to this NestJS app, my project key is segi_pk_live_…" and it will call the tools below to fetch the right install command, env vars, and code patches, and apply them.

Tools exposed

| Tool | Returns | | --- | --- | | get_install_command(packageManager) | The install command for pnpm, npm, yarn, or bun | | get_required_env_vars() | List of required + optional env vars with descriptions | | get_setup_files(publicKey?) | Patches for src/app.module.ts (SegiModule.forRoot) and src/main.ts (useGlobalFilters(new SegiExceptionFilter())) | | get_test_snippet() | A controller snippet to verify ingestion | | get_session_recording_info() | Stack-by-stack guidance: Next.js front-end → install @extn/segi-mcp-nextjs; Vite/CRA/SPA → use @extn/segi-js directly; plain HTML/CDN → needs a bundler. Includes the dashboard-side notes (off-by-default toggle, plan quotas) |

The MCP server is read-only — it only describes what to install and patch. The AI agent applies the changes.

Session recording

NestJS apps are server-only — they don't host the rrweb client. Call get_session_recording_info for stack-specific routing, or install @extn/segi-mcp-nextjs directly for the typical Nest API + Next.js front-end case. Recording quotas live on your organization plan; see Plans & Billing.

LLM guides

Single-file references the agent can fetch when this MCP isn't enough context:

• llms.txt index
• Error monitoring guide
• Session recording guide
• Plans & billing guide