Strategy for integrating (or not) third-party MCP servers, e.g. Sentry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
The Homepage New Tab team is looking to have an agent able to triage Sentry alerts in order to reduce time to root cause/remediation.
The strategy in question is - do we want to write our own MCP server (giving agents a limited set of tools backed by API integrations with the third-party), or do we want to proxy official third-party MCP servers?
Assumptions here are:
- We want to continue preventing the agent from accessing auth backed services directly (sidecar/proxy)
- We want explicit control over what actions are made available to the agent to perform its task
WIP PR towards a custom MCP for Sentry is here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing WIP PR #6705, which contains the custom Sentry MCP approach. Compare that approach with proxying an official third-party MCP server under the stated sidecar, authentication, and explicit-action constraints. Done means documenting and agreeing on the integration strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, backend-api-design, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100