Sentry is shipping a unified command-line and Model Context Protocol setup, so a single CLI login can also cover the company’s MCP server. David Cramer set the case out in a 10 November engineering post, “MCP or CLI? Yes.” The company’s X account pointed to the post the same day.
“Let’s stop debating it and just lean in: you can have both.”
— David Cramer, in MCP or CLI? Yes.
The new command, sentry mcp, launches the MCP server in stdio mode and adds a shim so it can use the credentials already held by the Sentry CLI. Cramer says you authenticate with the usual CLI methods, generally a device-code flow, and that login is passed through. The official Sentry MCP page documents the same local path: install the CLI, run sentry auth login, then register sentry mcp as a stdio server. “It uses the CLI login, so the MCP config needs no token,” the page says.
A Claude Code example on both the blog and the MCP page is claude mcp add sentry -- sentry mcp. Other clients can point at the same command. The MCP page still lists a separate HTTP endpoint at https://mcp.sentry.dev/mcp, which uses OAuth and can be scoped to an organisation or project.
Cramer’s case is that neither interface replaces the other. “The CLI can do things MCP can’t, and MCP is still the superior agentic tooling,” he wrote. The example he gives is session replay: the CLI has a filesystem, so an agent can pull chunks of a raw event log, grep them and paginate, which he says cannot be done efficiently through MCP alone. MCP, by contrast, is discovered natively: the agent does not know the CLI exists unless you tell it.
A later section sketches a future where launching MCP from the CLI would let the server steer the agent toward CLI commands for heavier work, but Cramer said Sentry has not implemented that transport-specific steering yet. The post calls the shared-login flow “the right solution right now for agents with access to sandboxes,” and “a new experiment.”
On authentication, Cramer said the main advantage is that Sentry controls the login flow, so “any of the historical authentication bugs in MCP are no longer present.” He also said this is not the perfect answer, and that he does not think it is the long-term one, because MCP’s consolidated authentication can support things like organisation-wide login and native token handling. The company says it is working on shifting onboarding toward a CLI-based approach, rather than a plugin-based one, and has asked for feedback from people who try the new flow.
Discover more from Sulat AI & Tech News
Subscribe to get the latest posts sent to your email.
