Add 'sentry mcp' subcommand to run MCP server in stdio mode

Open
#1,220 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
authentication, cli

Research direction

Start by inspecting the existing sentry subcommand entry points and auth stack used by sentry login, including resolution of stored credentials and SENTRY_AUTH_TOKEN. Determine whether to depend on or exec sentry-mcp; done means sentry mcp launches it in stdio mode and supports the shown MCP client configuration without manual token setup.

Written by the indexing model from the issue text.

Description

enhancement

Add a sentry mcp subcommand that launches the sentry-mcp server in stdio mode, automatically binding the access token from the CLI's existing auth stack — no manual token configuration required.

Current behavior

Users must run sentry-mcp as a separate tool and manually supply an access token. There's no path to launch the MCP server with credentials already managed by the CLI.

Gap

  • MCP clients (Claude, Cursor, etc.) need a single shell command to wire up the Sentry MCP server. Wrapping it as sentry mcp gives users a zero-config entry point that reuses their existing sentry login credentials.
  • Without this, discoverability and setup friction are high — users have to know about sentry-mcp as a separate package and obtain a token independently.

Implementation notes

  • Can be done pre-repo merge by having sentry-cli take a dependency on sentry-mcp (or exec it) and invoking it in --transport stdio mode.
  • Auth binding should follow the same resolution order the CLI already uses: stored credentials → SENTRY_AUTH_TOKEN env var.
  • MCP client config would simplify to: { "command": "sentry", "args": ["mcp"] }.

--

View Junior Session in Sentry

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.