Sentry MCP server only connects to US region - can I set a custom API base URL?
I'm using the official Sentry MCP server from the modelcontextprotocol/servers repository. It only uses the default US-based Sentry API, so organizations with data in the EU can't retrieve their issues. Is there a way to configure the API base URL, or is that not supported?
Originally asked on GitHub: https://github.com/modelcontextprotocol/servers/issues/514
1 answer
Status: explained - the request is closed as NOT_PLANNED, and a project member said the server was moved to the archived modelcontextprotocol/servers-archived repository to reduce maintenance overhead.
The issue asked for the ability to use the server with data in the European Union, and a comment also requested support for self-hosted Sentry instances by making the API URL configurable. No such option was added in this thread. A project member replied that the server is no longer actively maintained and pointed to the alternatives listed in the official integrations section of the modelcontextprotocol/servers README.
General advice: if you need EU-region or self-hosted Sentry support, look for a community-maintained Sentry MCP server that exposes a configurable base URL or API endpoint, and check its authentication requirements before using it.
Did this work for you?
Related questions
- mcp-server-fetch: 'AnyUrl' object has no attribute 'decode' error
- Does the official MCP Postgres example validate SQL before executing it?
- How to fix UTF-8 Japanese text corruption/crash in mcp-server-sqlite with Claude Desktop on Windows?
- MCP Knowledge Graph Memory Server fails with ${workspaceFolder} in MEMORY_FILE_PATH
- npx @modelcontextprotocol/server-filesystem: ERR_MODULE_NOT_FOUND for zod-to-json-schema