# Add to your Claude Code skills
git clone https://github.com/getsentry/toolkitGuides for using ai agents skills like toolkit.
Last scanned: 10/2/2026
{
"issues": [
{
"file": "packages/cli/plugins/sentry-cli/skills/sentry-cli/SKILL.md",
"line": 356,
"type": "remote-install",
"message": "Install command (remote install script piped to a shell — review the source before running): \"curl https://cli.sentry.dev/install -fsS | bash\"",
"severity": "medium"
}
],
"status": "PASSED",
"scannedAt": "2026-10-02T10:20:06.244Z",
"npmAuditRan": false,
"pipAuditRan": true,
"promptInjectionRan": true
}See how toolkit compares with popular alternatives.
toolkit is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by getsentry. Agentic tooling for Sentry. It has 964 GitHub stars.
Yes. toolkit passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/getsentry/toolkit" and add it to your Claude Code skills directory (see the Installation section above).
toolkit is primarily written in TypeScript. It is open-source under getsentry on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh toolkit against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
This repository contains the Sentry CLI, the Sentry MCP server, and shared packages. For the CLI, see the CLI guide and the published documentation at https://cli.sentry.dev/. The documentation index covers both products and shared contributor guidance.
The independent Docs MCP Worker provides documentation
search and AI-generated answers backed by docs.sentry.io.
Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality.
This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools. It's based on Cloudflare's work towards remote MCPs.
You'll find everything you need to know by visiting the deployed service in production:
If you're looking to contribute, learn how it works, or to run this for self-hosted Sentry, continue below.
Install as a Claude Code plugin for automatic subagent delegation:
claude plugin marketplace add getsentry/sentry-mcp
claude plugin install sentry-mcp@sentry-mcp
This provides a sentry-mcp subagent that Claude automatically delegates to when you ask about Sentry errors, issues, traces, or performance.
For forward-looking tool variants and features:
claude plugin install sentry-mcp@sentry-mcp-experimental
While this repository is focused on acting as an MCP service, we also support a stdio transport. It is the easiest way to run the MCP server against a self-hosted Sentry install.
Note: The AI-powered search tools (search_errors, search_traces, search_logs, search_issues, etc.) require an LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter). These tools use natural language processing to translate queries into Sentry's query syntax. Without a configured provider, these specific tools will be unavailable, but all other tools will function normally.
Run the stdio server with the Sentry CLI's sentry mcp command. It uses your CLI login, so the MCP config needs no token:
curl https://cli.sentry.dev/install -fsS | bash
sentry auth login
claude mcp add sentry -- sentry mcp
The CLI also installs with brew install getsentry/tools/sentry,
npm install -g sentry, or irm https://cli.sentry.dev/install.ps1 | iex on
Windows. See the CLI installation guide.
Other clients take the same command:
{
"mcpServers": {
"sentry": {
"command": "sentry",
"args": ["mcp"]
}
}
}
Pass <org>/ or <org>/<project> to limit every call to one organization or
project (sentry mcp acme/, sentry mcp acme/web), and --experimental for
forward-looking tool variants. Run sentry mcp --help for every flag and
environment variable, or see the sentry mcp docs.
SENTRY_AUTH_TOKEN, when set, wins over the stored login. See
docs/operations/stdio-auth.md.
To use a token, create a User Auth Token in Sentry with the necessary scopes. As of writing this is:
org:read
project:read
project:write
team:read
team:write
event:write
Need to connect to a self-hosted deployment? Log in to it with
sentry auth login --url https://sentry.example.com, then set
SENTRY_HOST (e.g. SENTRY_HOST=sentry.example.com)
in the MCP server's environment, which also scopes
SENTRY_AUTH_TOKEN to that server. For isolated internal
deployments that only expose plain HTTP, use an http://
SENTRY_URL instead. See the
CLI self-hosted guide.
Seer is not part of self-hosted Sentry, so the seer skill is left out of the
default skill set whenever the host is not sentry.io. If your
self-hosted deployment does run Seer, opt back in explicitly:
SENTRY_HOST=sentry.example.com sentry mcp --skills=inspect,seer
You can also disable any other skill to prevent unsupported tools from being exposed:
SENTRY_HOST=sentry.example.com sentry mcp --disable-skills=project-management
For self-hosted instances without TLS:
SENTRY_URL=http://sentry.internal:9000 sentry mcp
@sentry/mcp-server still
ships the same server, bundled without the rest of the CLI, for clients that
launch it through npx. It shares the CLI's login and takes the same flags and
environment variables:
npx @sentry/mcp-server@latest auth login # once, to sign in
npx @sentry/mcp-server@latest # uses that login
SENTRY_AUTH_TOKEN=sentry-user-token npx @sentry/mcp-server@latest
--access-token / SENTRY_ACCESS_TOKEN from older releases still work but are
deprecated: they act as SENTRY_AUTH_TOKEN and print a warning on stderr.
Remote clients that support custom HTTP headers can pass an upstream Sentry API token directly to the Cloudflare transport:
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp",
"headers": {
"Authorization": "Sentry-Bearer ${SENTRY_ACCESS_TOKEN}"
}
}
}
}
Sentry-Bearer is intentionally separate from Bearer: Bearer is reserved
for MCP OAuth access tokens. With Sentry-Bearer, the worker does not store,
validate, exchange, or refresh the upstream token. It forwards the token through
the same Sentry API calls used by OAuth-backed sessions, and the client or
upstream provider remains responsible for token lifetime and refresh.
Direct remote auth defaults to all active MCP skills. You can narrow the exposed
tools with ?skills=inspect,triage or ?disable-skills=seer.
SENTRY_AUTH_TOKEN= # Optional after `auth login`; wins over a stored login
# LLM Provider Configuration (required for AI-powered search tools)
EMBEDDED_AGENT_PROVIDER= # Required when multiple provider keys are set: 'openai', 'azure-openai', 'anthropic', or 'openrouter'
OPENAI_API_KEY= # Required if using OpenAI
ANTHROPIC_API_KEY= # Required if using Anthropic
OPENROUTER_API_KEY= # Required if using OpenRouter
OPENROUTER_MODEL= # Optional OpenRouter model, defaults to 'openai/gpt-5.6-luna'
OPENROUTER_REASONING_EFFORT= # Optional OpenRouter reasoning effort, defaults to 'high'
# Optional overrides
SENTRY_HOST= # For self-hosted deployments (drops 'seer' from the default skills)
MCP_SKILLS= # Grant specific skills (comma-separated, e.g. 'inspect,seer')
MCP_DISABLE_SKILLS= # Disable specific skills (comma-separated, e.g. 'project-management')
Important: Always set EMBEDDED_AGENT_PROVIDER to explicitly specify your LLM provider. Auto-detection based on API keys alone is deprecated and will be removed in a future release. See docs/operations/embedded-agents.md for detailed configuration options.
{
"mcpServers": {
"sentry": {
"command": "sentry",
"args": ["mcp"],
"env": {
"EMBEDDED_AGENT_PROVIDER": "openai",
"OPENAI_API_KEY": "sk-..."
}
}
}
}
If you leave the host variable unset, the CLI automatically targets the Sentry SaaS service. Only set the override when you operate self-hosted Sentry.
Setting SENTRY_HOST to a self-hosted host also drops the seer skill from
the default set, since Seer is not available on self-hosted Sentry. For a
self-hosted deployment that does run Seer, opt in with MCP_SKILLS:
{
"mcpServers": {
"sentry": {
"command": "sentry",
"args": ["mcp"],
"env": {
"SENTRY_HOST": "sentry.example.com",
"MCP_SKILLS": "inspect,seer"
}
}
}
}
Tool calls are subject to the Sentry API's rate limits. The MCP server retries rate-limited requests, and transient Sentry server errors on read requests, after a short wait. When a limit lasts longer, the tool returns a Rate Limited message that says when to try again. Agents hit the per-second limits most often by running many Sentry tool calls in parallel, so run them one at a time if you see this message.
MCP includes an Inspector, to easily test the service:
pnpm inspector
Enter the MCP server URL (http://localhost:5173) and hit connect. This should trigger the authentication flow for you.
Note: If you have issues with your OAuth flow when accessing the inspector on 127.0.0.1, try using localhost instead by visiting http://localhost:6274.
To contribute changes, you'll need to set up your local environment:
Set up environment and agent skills:
make setup-env # Creates .env files and installs shared agent skills
This also runs npx @sentry/dotagents install to install shared skills from getsentry/skills into .agents/skills/ (symlinked into .claude/skills and .cursor/skills). If you need to update skills later, run it directly:
npx @sentry/dotagents install
Create an OAuth App in Sentry (Settings => API => Applications):
http://localhost:5173