MCP Recipe
Triage a Sentry error with Sentry and Context7
Influzer starter recipe: pull a recent Sentry issue, map the stack to the likely code path, then check current library docs with Context7 before proposing a fix.
MCP servers used
Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, Claude Code, ChatGPT
Prerequisites
- Sentry remote MCP access to an org/project you own
- Context7 remote MCP access
- Local repo open in the client when you want code-level fixes
Required permissions
Sentry OAuth can expose error payloads and PII depending on your project settings — scrub before sharing externally. Context7 is read-only docs lookup.
Setup
Add Sentry at https://mcp.sentry.dev/mcp and complete OAuth for your org. Add Context7 at https://mcp.context7.com/mcp.
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
},
"context7": {
"url": "https://mcp.context7.com/mcp"
}
}
}
Using Sentry, fetch the most frequent unresolved issue from the last 24 hours in my primary project.
Summarize title, culprit, event count, and the top stack frames (scrub PII).
If a third-party library appears in the stack, use Context7 for that library’s current error-handling docs.
Propose a minimal fix and a regression test idea. Do not deploy anything.
Expected result
A triage note: issue summary, suspected root cause, Context7-backed API notes, and a minimal proposed fix.
Sample output
Issue: TypeError on /checkout (24 events / 6h)
Suspect: null session.customer after Stripe redirect
Context7 (stripe): PaymentIntent status handling…
Proposed fix: guard + redirect to /login when customer is missing.
Troubleshooting
- Sentry auth loop: remove and re-add
https://mcp.sentry.dev/mcp - Wrong project: name the org/project in the prompt
- Never paste production DSN secrets into chat — configure them in Sentry / client settings