The Sentry MCP server is an open protocol designed to standardize context bringing into LLM interactions, and it has been added by Sentry as a hosted/remote solution. The MCP server supports various features such as remote hosted mode, OAuth support for logging in via existing Sentry organizations, Streamable HTTP with fallback to SSE if the client doesn't support it, and 16 different tool calls that can be used to bring wide context from Sentry into LLMs. These tool calls include project information, issues, finding or creating projects, and even calling the AI agent Seer to generate root causes and fix issues. The MCP server is designed to be low-friction and easy to consume as a service, with support for OAuth and Streamable HTTP. It can be added to most providers that support OAuth by adding specific content to the MCP configuration file. The Sentry MCP server is intended to bring context into LLMs, allowing them to use tool calls such as `list_projects` to access project information and chain together different tool calls to kick off Seer's analysis run. While MCP is designed for bringing context into LLMs, it is not built for debugging, and tools like Seer are purpose-built for understanding why applications break and how to fix them. The Sentry MCP server has made significant progress in a short period of time and is expected to continue growing in popularity and functionality.