RevampKeyRevampKey home
Download

Set up Sentry for a new app with AI

Adds Sentry to an app: creates or reuses the team and project, gets the DSN, and follows Sentry's current docs for your framework, covering SDK install, releases and source maps, then checks that a test error arrives.

Asks before writingUses 10 Sentry toolsWorks in RevampKey, Claude Code, Codex and Cursor

Use in RevampKey

Get RevampKey to connect Sentry

RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Sentry is one click away with its skills already attached.

Download RevampKey

Not now? Use the skills in your current tool

curl -fsSL --create-dirs -o .claude/skills/sentry-project-setup/SKILL.md https://revampkey.com/marketplace/sentry/skills/project-setup/SKILL.md
Other agents
Other agents

When to use it

  • Starting a new service or app
  • Moving to Sentry from another error tracker
  • Fixing missing source maps or releases

What it looks like

You

Add Sentry to this Next.js app.

find_teamsfind_projectsfind_dsnscreate_team+6 more
Agent

No existing project for this app. Proposed: project "web-dashboard" (platform javascript-nextjs) under team Frontend. After that I will add @sentry/nextjs, the three config files and source map upload with the DSN in SENTRY_DSN. Create the project?

The SKILL.md file

View raw
name: sentry-project-setup

Set up Sentry for a new app or service by creating or picking the team and project, getting the DSN, and walking through SDK install, release tracking and source maps from Sentry's docs. Use when the user asks to add Sentry to a project, create a Sentry project, or get a DSN.

Steps

  1. Identify the platform from the user's repo or words, such as Next.js, Django, React Native or Go.
  2. Check what exists with find_teams, find_projects and find_dsns, to avoid duplicate projects.
  3. If a new project is needed, propose the team, project name and platform. After the user approves, create it with create_team (only if no team fits) and create_project, and adjust settings with update_project when asked. Use create_dsn only when the user wants a separate key, for example per environment.
  4. Fetch the setup guide for that platform with search_docs and get_doc. Follow the current docs, not memory: SDK init, environment, release name, and source maps or debug symbols.
  5. When the repo is open, propose the exact code and config changes. Keep the DSN in an environment variable, not hard-coded.
  6. Verify by asking the user to trigger a test error, then confirm it arrived with find_issues.

Report

The project, DSN location and the files changed, plus what remains, such as uploading source maps in CI.

Sentry tools it uses

  • find_teams
  • find_projects
  • find_dsns
  • create_teamAsks first
  • create_projectAsks first
  • update_projectAsks first
  • create_dsnAsks first
  • search_docs
  • get_doc
  • find_issues

Tool list from Sentry MCP documentation.

FAQ

Does it use current Sentry docs?

Yes. It fetches the setup guide for your platform from Sentry's documentation each time, rather than relying on memory.

Where does the DSN go?

In an environment variable. The skill never hard-codes it in source.