Arlet
Sentry

Connect Sentry to Copilot Studio

Search, read and write Sentry from Copilot Studio. Arlet links the two through one MCP connection and takes care of keys and authentication.

Enable Sentry in ArletCopilot Studio connection guide (docs)

Arlet makes Sentry's official MCP server available from the AI client you already use. Signing in completes the connection, and the consent screen lets you choose which permission sets (inspect, Seer, triage, project management) to grant.

The AI can search issues and events, read stack traces and traces, run Seer root-cause analysis, and update or comment on issues. The available tools are those provided by Sentry's official server.

How to connect Sentry to Copilot Studio

  1. 1

    In the Arlet dashboard, open Integrations → Add an integration and choose Sentry. Sign in with Link Sentry, name the connection and click Create.

  2. 2

    Sign in to Copilot Studio with your work account, create a new agent (or open an existing one), and in the Build tab choose Tools → + → Add → Model Context Protocol (MCP) in the right panel.

  3. 3

    In the Add MCP server form, enter "Arlet" as the Server name, https://mcp.arlet.dev/mcp/ as the Server URL, choose OAuth 2.0 for Authentication and "Dynamic (detected)" for Configuration type, then click Add. No Client ID / Secret is needed.

  4. 4

    On the Select a connection screen, choose Create new connection → Create, then sign in with Google on the Arlet authorization screen and click Allow. Click Add to attach the tool to the agent, then Publish to use it from Microsoft 365 Copilot.

Requires a Microsoft work account and a Copilot Studio license (or trial). MCP is available only for agents using generative orchestration and not in Copilot Studio in Teams.

What you can do

Sentry tools that Copilot Studio can call.

  • search_issues

    Search issues with natural-language conditions.

  • search_events

    Search events and replays, with counts and trends.

  • get_issue_details

    Get an issue's details, impact and stack trace.

  • get_event_stacktrace

    Get an event's stack trace.

  • get_trace_details

    Get a trace's spans and timings.

  • analyze_issue_with_seer

    Run Seer root-cause analysis with fix suggestions.

  • update_issue

    Change an issue's status or assignee.

  • add_issue_note

    Comment on an issue.

  • find_releases

    Search releases.

  • get_release_details

    Get a release's details.

  • find_alert_rules

    List alert rules.

  • find_monitors

    List cron monitors.

  • find_dashboards

    Search dashboards.

  • find_projects

    List projects.

  • search_docs

    Search Sentry's documentation.

The tool list follows what Sentry's official MCP server provides and may change.

Example uses

  • First-response investigation

    Find issues that spiked in the last 24 hours and summarize stack traces and impact for the team.

  • Root-cause analysis

    Analyze an issue with Seer and turn the explanation and suggested fix into a review-ready note.

  • Triage

    Rank open issues by severity, assign owners and leave notes.

  • Release health

    List issues new to the latest release to decide whether to roll back.

Prompts you can use as-is

  • List issues whose event count spiked in the last 24 hours, sorted by affected users
  • Analyze issue PROJ-1234 with Seer and explain the cause and the fix
  • Rank open issues by severity and assign the top five to me
  • List the issues that first appeared in release 2.14.0

Use Sentry with other AI clients