[No QA] Add Sentry MCP server for Claude Code integration by sosek108 · Pull Request #86231 · Expensify/App

sosek108 · 2026-03-24T14:49:33Z

Explanation of Change

Adds the Sentry MCP server to the project's Claude Code configuration. This gives engineers using Claude Code direct access to Sentry — they can search issues, inspect events and traces, and run AI-assisted analysis (Seer) without leaving the editor.

Three files changed:

.mcp.json — registers the Sentry MCP server via its OAuth remote HTTP endpoint (https://mcp.sentry.dev/mcp). No API token setup required; Claude Code will prompt for a one-time browser OAuth login on first use.
.claude/settings.json — adds all mcp__sentry__* tool permissions to the allow list so Claude Code can call them without prompting.
CLAUDE.md — documents the Sentry MCP setup, how OAuth works, and example use cases for engineers onboarding.

This is a dev-tooling-only change. It has no effect on the application runtime, tests, or CI.

Fixed Issues

$ #86314
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-03-26T09:05:18Z

@grgia Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

grgia

LGTM given it's only accessible to those with sentry access

grgia · 2026-03-26T10:28:11Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

kacper-mikolajczak · 2026-03-26T10:29:41Z

+| `mcp__sentry__search_issue_events` | Get individual events for a known issue ID |
+| `mcp__sentry__get_issue_tag_values` | Inspect tag distributions (e.g. device, version) on an issue |
+| `mcp__sentry__get_sentry_resource` | Fetch a specific Sentry resource by URL/ID |
+


mcp__sentry__get_sentry_resource is listed in this table but is absent from the allowedTools list in .claude/settings.json. Was that intentional?

kacper-mikolajczak · 2026-03-26T10:29:41Z

+            "mcp__sentry__search_issue_events",
+            "mcp__sentry__search_issues",
+            "mcp__sentry__whoami"
        ]


Several tools are pre-approved here but don't appear in the SKILL.md reference table: find_organizations, find_projects, find_teams, get_doc, search_docs, get_event_attachment, get_trace_details, whoami. Were these intentionally left out of the docs?

github-actions · 2026-03-26T10:29:42Z

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-03-26T10:35:16Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #86231.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-482e0d7-23e70e6-1499fe4b3727545e9a9a0a4f1b166514b55ab6e7/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-482e0d7-23e70e6-78af505a931d03be02d452fb006d4b15c9fdcebd/index.html

Web 🕸️
https://86231.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-26T10:37:32Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-03-26T14:42:56Z

🚀 Deployed to staging by https://github.com/grgia in version: 9.3.49-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

OSBotify · 2026-03-27T12:25:04Z

🚀 Deployed to production by https://github.com/grgia in version: 9.3.49-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

chore: add Sentry MCP server integration

f317d15

melvin-bot Bot assigned sosek108 Mar 24, 2026

sosek108 added 2 commits March 24, 2026 15:57

remove seer mention

918602c

fix prettier errors

62a7b96

sosek108 marked this pull request as ready for review March 26, 2026 09:04

sosek108 requested a review from a team as a code owner March 26, 2026 09:04

melvin-bot Bot requested review from grgia and removed request for a team March 26, 2026 09:05

sosek108 added 4 commits March 26, 2026 10:47

move some info about MCP to sentry/SKILL.md

01cf3bd

spellcheck

642c4c9

update to SKILL.md

ac16572

remove seer tool

5d2d17c

grgia approved these changes Mar 26, 2026

View reviewed changes

grgia merged commit 482e0d7 into Expensify:main Mar 26, 2026
18 of 19 checks passed

kacper-mikolajczak reviewed Mar 26, 2026

View reviewed changes

OSBotify mentioned this pull request Mar 26, 2026

Deploy Checklist: New Expensify 2026-03-26 #86439

Closed

29 tasks

melvin-bot Bot mentioned this pull request Mar 27, 2026

[Due for payment 2026-04-03] Surface Sentry in Claude Code #86314

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[No QA] Add Sentry MCP server for Claude Code integration#86231

[No QA] Add Sentry MCP server for Claude Code integration#86231
grgia merged 7 commits into
Expensify:mainfrom
callstack-internal:wt1

sosek108 commented Mar 24, 2026 •

edited

Loading

Uh oh!

melvin-bot Bot commented Mar 26, 2026

Uh oh!

grgia left a comment

Uh oh!

grgia commented Mar 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

kacper-mikolajczak Mar 26, 2026 •

edited

Loading

Uh oh!

kacper-mikolajczak Mar 26, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

sosek108 commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Mar 26, 2026

Uh oh!

grgia left a comment

Choose a reason for hiding this comment

Uh oh!

grgia commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

kacper-mikolajczak Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kacper-mikolajczak Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

sosek108 commented Mar 24, 2026 •

edited

Loading

grgia commented Mar 26, 2026 •

edited

Loading

kacper-mikolajczak Mar 26, 2026 •

edited

Loading

kacper-mikolajczak Mar 26, 2026 •

edited

Loading