MCP / Developer tools
Sentry MCP
Sentry issues/errors, projects, releases, DSNs + Seer AI root-cause. Connect it to Claude, Codex, Cursor or any MCP client through one FlyMy.AI MCP.
List the unresolved Sentry issues in the web project from the last 24 hours, newest first.
Paste it into an assistant connected to FlyMy.AI. The agent picks the actions.
What Sentry MCP can do
16 actions in the FlyMy.AI catalog, the most used first. Your agent finds them through search_tools and calls the one the task needs.
| Action | What it does |
|---|---|
get_sentry_resource | Fetch a Sentry resource by URL, or by resourceType plus resourceId. |
search_issues | Search for grouped issues/problems in Sentry - returns a LIST of issues, NOT counts or aggregations. |
search_events | Search Sentry events and replays. Use for event counts/statistics. `query` can be natural language or Sentry search syntax. |
analyze_issue_with_seer | Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes. |
execute_sentry_tool | Execute an available Sentry MCP tool discovered through search_sentry_tools. |
find_dropped_events | Find events dropped before they were stored in Sentry - ground-truth data-fidelity information about what was and wasn't captured. |
find_organizations | Find organizations that the user has access to in Sentry. |
find_projects | Find projects in Sentry. Use this tool when you need to: - View projects in a Sentry organization - Find a project's slug to aid other tool requests - Search for specific projects by name or slug. |
search_errors | Search Sentry error events: exceptions and crashes with stack traces. |
search_logs | Search Sentry logs: application log entries, including error- and warning-severity log messages. |
search_metrics | Search Sentry metrics: counters, gauges, and distributions, as rows or aggregates. |
search_profiles | Search Sentry profiles: transaction and continuous profile results, profile IDs, and profiled transactions. |
Show all 16 actions
| Action | What it does |
|---|---|
search_replays | Search Sentry session replays: rage clicks, dead clicks, visited pages, errors seen, and replay users. `query` is natural language (preferred) or replay search syntax; a configured agent... |
search_sentry_tools | Search the available Sentry MCP tool catalog by name and description. |
search_traces | Search Sentry spans and traces: requests, API/HTTP calls, endpoints, DB queries, AI/LLM calls, and other operations. |
update_issue | Update a Sentry issue's status or assignment. |
Ask your agent
Requests to paste as they are. Each one runs on the actions named under it.
search_issuessearch_eventsanalyze_issue_with_seersearch_replaysConnect Sentry in a minute
One MCP for every integration. Add it once, then every MCP in the catalog is a request away.
- 01
Add FlyMy.AI
Add the FlyMy.AI MCP to your assistant with one of the commands below and sign in. No key to copy.
- 02
Sign in to Sentry
Open the Sentry connection settings and sign in once. Your agent then works as your account; the token stays with FlyMy.AI, never in a prompt or a chat.
- 03
Ask
Paste a request from this page. Every run shows what it cost.
claude mcp add --transport http flymyai https://mcp-agents.flymy.ai/mcp
Then run /mcp in Claude Code and sign in.
codex mcp add flymy --url https://mcp-agents.flymy.ai/mcp
Then run codex mcp login flymy to sign in.
https://mcp-agents.flymy.ai/mcp
Settings, Connectors, Add custom connector: paste this URL.
Pay per run
FlyMy.AI bills the run: the model and the tool's seconds. Calls go to your own Sentry account, under its plan and limits. No seats and no minimum.
Go to the source
From the FlyMy.AI platform catalog of 2026-10-28: name, description, actions and setup as the platform lists them. Examples are requests to paste, not recorded runs.