Schema | sentry-self-hosted-mcp

sentry-self-hosted-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`SENTRY_HOST`	Yes	Your Sentry URL (e.g., https://sentry.example.com)
`SENTRY_TOKEN`	Yes	Auth token with org:read, project:read, event:read scopes
`SENTRY_ORG_SLUG`	Yes	Organization slug (e.g., my-org)

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
get_eventA	Get detailed information about a specific Sentry event by project slug and event ID. Returns exception details, stacktrace, tags, and context.
get_issueB	Get information about a Sentry issue by its numeric ID or short ID (e.g. "PAYOUT-123"). Includes status, event count, first/last seen.
get_latest_eventB	Get the latest event for a Sentry issue.
list_issuesB	List Sentry issues with optional filters. Supports search queries like "is:unresolved", "level:error", etc.
list_projectsA	List all Sentry projects in the organization.
get_stack_framesA	Extract and format stack frames from a Sentry event. Useful for quickly seeing the call chain without full event details.
get_issue_with_stacktraceB	Get issue metadata and latest event stacktrace in a single call.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vitalypanait/sentry-self-hosted-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server