MCP Docs: Update for OAuth configs, web client, troubleshooting details. (#14142)

Updating Sentry MCP docs - 
* New configs for OAuth 
* Details for additional clients like Claude Code, additions for Cursor
1.0, and mcp.sentry.dev web client
* Additional troubleshooting details 
* Bringing additional content from mcp landing page

Author: codyde

docs/product/sentry-mcp/img/mcpdev.png

@@ -5,7 +5,7 @@ description: "Enable secure connectivity between Sentry issues and debugging dat
 ---
 
 <Alert>
-  The Sentry MCP Server is currently in **beta**. Beta features are still a work in progress and may have bugs. Please reach out on
+  The Sentry MCP Server has been released for production, however MCP is a developing technology and changes should be expected. There will be bugs. Please reach out on
   [GitHub](https://github.com/getsentry/sentry-mcp/issues) if you have any feedback or concerns.
 </Alert>
 
@@ -19,67 +19,197 @@ The [Sentry MCP Server](https://mcp.sentry.dev) provides a secure way of bringin
 - List and create Sentry DSN's for projects
 - Invoke Seer to automatically fix issues and retrieve the status and details of an issue fix
 
+The Sentry MCP Server includes support for modern MCP features:
+
+- **Remote hosted (preferred) or local STDIO mode** - The hosted version provides lower friction and always includes the latest functionality and stability
+- **OAuth support** - Authenticate using your existing Sentry organization for seamless access to your projects
+- **Streamable HTTP with graceful SSE fallback** - Automatic fallback ensures compatibility across different clients
+- **16+ tool calls and prompts** - Comprehensive toolset for bringing Sentry context into LLM interactions
+
 <VimeoEmbed id="1080588938?h=1e437d4874" />
 
 ## Getting Started
 
-Most clients that natively support MCP can be configured using a mcp_config.json file or an equivalent. In these systems, adding the server configuration to the file will setup an MCP server: 
+### OAuth Configuration (Recommended)
+
+For clients that support OAuth, you can use the streamlined configuration that provides automatic authentication:
 
 ```json
 {
-    "mcpServers": {
-        "Sentry": {
-            "command": "npx",
-            "args": [
-                "mcp-remote@latest",
-                "https://mcp.sentry.dev/sse"
-            ]
-        }
+  "mcpServers": {
+    "Sentry": {
+      "url": "https://mcp.sentry.dev/mcp"
     }
+  }
 }
 ```
 
-This setup uses the Remote-MCP server configuration, enabling most clients to connect to the Sentry MCP, authenticate via OAuth, and access the available tools.
+This configuration:
+- Enables OAuth authentication with your Sentry organization
+- Uses Streamable HTTP transport with automatic SSE fallback
+- Provides access to all 16+ available tools
+- Automatically handles authentication and session management
 
-Alternatively, if you don't want the Remote-MCP server, you can run the MCP Server locally in STDIO mode by following the instructions in the [README](https://github.com/getsentry/sentry-mcp).
+With OAuth configuration, you'll be prompted to:
+1. Accept the OAuth authorization
+2. Login via your existing Sentry organization
+3. Grant access to the necessary permissions
 
-Once configured via one of these methods, you'll be able to view the available tools within your client and use them as part of your LLM calls.
+Once authenticated, you'll see the tools become available in your MCP client.
 
 ![Available Sentry MCP Tools](./img/mcp-tools.png)
 
-## Example Calls 
+### Remote MCP Configuration (Legacy)
 
-- Tell me about the issues in my `project`
-- Check Sentry for errors in `file.tsx` and propose solutions.
-- Diagnose issue `issue id` and propose solutions.
-- Create a new project in Sentry for `service-name` and setup local instrumentation using it.
-- Use Sentry's Seer and help me analyze and propose a solution for `issue id`.
+For clients that don't support OAuth, you can continue using the existing Remote MCP endpoint configuration:
 
-![Sentry MCP using Autofix](./img/mcp-autofix1.png)
+```json
+{
+  "mcpServers": {
+    "Sentry": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "mcp-remote@latest",
+        "https://mcp.sentry.dev/mcp"
+      ]
+    }
+  }
+}
+```
+
+### Local STDIO Mode
+
+Alternatively, if you don't want the Remote-MCP server, you can run the MCP Server locally in STDIO mode by following the instructions in the [README](https://github.com/getsentry/sentry-mcp). This is particularly useful for self-hosted Sentry installations.
+
+To use STDIO mode, you'll need a Sentry User Auth Token with the following scopes:
+- `org:read`
+- `project:read`
+- `project:write`
+- `team:read`
+- `team:write`
+- `event:write`
+
+Launch the STDIO transport:
+
+```bash
+npx @sentry/mcp-server@latest --access-token=sentry-user-token --host=sentry.example.com
+```
+
+You can also use environment variables:
+```bash
+SENTRY_ACCESS_TOKEN=your-token
+SENTRY_HOST=your-sentry-host
+```
+
+### mcp.sentry.dev (live demo)
+
+The [Sentry MCP page](https://mcp.sentry.dev) provides a simple way to configure and test the MCP server. From this web client you can authenticate with your Sentry organization and access a hosted MCP server for testing. 
+
+![Sentry MCP live demo](./img/mcpdev.png)
+
+## Available Tools
+
+The Sentry MCP Server provides comprehensive tools for interacting with Sentry data:
+
+### Core Tools
+- **Organizations**: List and query organization information
+- **Projects**: Find, list, and create projects
+- **Teams**: Manage and query team information
+- **Issues**: Access issue details, search, and analyze problems
+- **DSNs**: List and create Data Source Names for projects
+
+### Analysis Tools
+- **Error Searching**: Find errors in specific files or across projects
+- **Issue Analysis**: Detailed issue investigation with context
+- **Seer Integration**: Invoke Sentry's AI agent for root cause analysis and automated fixes
 
-TODO: Image needs to be updated
+### Advanced Features
+- **Release Management**: Query and analyze release information
+- **Performance Monitoring**: Access transaction and performance data
+- **Custom Queries**: Execute complex searches across Sentry data
+
+## Example Usage
+
+Here are some example prompts you can use with the Sentry MCP:
+
+- Tell me about the issues in my `project-name`
+- Check Sentry for errors in `components/UserProfile.tsx` and propose solutions
+- Diagnose issue `PROJECT-123` and propose solutions
+- Create a new project in Sentry for `new-service-name` and setup local instrumentation
+- Use Sentry's Seer to analyze and propose a solution for issue `PROJECT-456`
+- Show me the most recent releases for my organization
+- Find all unresolved crashes in my React Native app
+
+![Sentry MCP using Autofix](./img/mcp-autofix1.png)
 
 ## Verified Clients 
 
 The Sentry MCP Server has been verified to work in: 
 
 ### Claude for Desktop 
 
-By accessing the developer tools via `CMD + ,` -> `Developer` -> `Edit Config` -> edit the `claude_desktop_config.json` file 
+Access developer tools via `CMD + ,` → `Developer` → `Edit Config` → edit the `claude_desktop_config.json` file
 
 ### Claude.ai 
 
-You can access the `Settings` -> `Profile` -> Scroll to `Integrations`, select `Add More`, and add the Sentry MCP server URL `https://mcp.sentry.dev/sse`
+Navigate to `Settings` → `Profile` → Scroll to `Integrations`, select `Add More`, and add the Sentry MCP server URL `https://mcp.sentry.dev/mcp`
 
-### Windsurf
+### Claude Code 
 
-Via the `Configure MCP` option in Cascade (CMD + L)
+Since recently reaching 1.0, Claude Code has native support for remote hosted MCP servers. From your cli enter `claude mcp add --transport http sentry https://mcp.sentry.dev/mcp` and then access Claude Code with `claude`. 
+
+Once in, you'll be prompted to authenticate with OAuth to Sentry. 
 
 ### Cursor
 
-Via the `Cursor` -> `Settings` -> `Cursor Settings` -> `MCP` and editing the `mcp.json` file
+Available via `Cursor` → `Settings` → `Cursor Settings` → `MCP` following the promps to configure Sentry MCP. Cursor 1.0+ includes enhanced MCP support with OAuth and Streamable HTTP.
+
+You can still edit the `mcp.json` file manually if you prefer. 
 
 ### VS Code and GitHub Copilot
 
-By adding the server in `CMD+Shift+P` and selecting `MCP: Add Server`
+Add the server using `CMD+Shift+P` and selecting `MCP: Add Server`
+
+### Windsurf
+
+Configure via the `Configure MCP` option in Cascade (CMD + L)
+
+### Other Clients
+
+The Sentry MCP Server follows standard MCP protocols and should work with any client that supports:
+- OAuth authentication (recommended)
+- Remote MCP servers
+- SSE or Streamable HTTP transport
+
+## Integration with Seer
+
+The Sentry MCP Server provides seamless integration with [Seer](/product/ai-in-sentry/seer/), Sentry's AI agent. You can:
+
+- **Trigger Seer Analysis**: Initiate automated root cause analysis for issues
+- **Get Fix Recommendations**: Receive AI-generated solutions for bugs and performance issues
+- **Monitor Fix Status**: Track the progress of Seer's analysis and implementation
+
+**Note**: MCP and Seer are complementary tools. MCP brings Sentry context into your LLM, while Seer is purpose-built for deep issue analysis and automated debugging. You can use MCP to invoke Seer for complex debugging workflows.
+
+## Troubleshooting
+
+### Common Issues
+
+**OAuth Authentication Problems**
+- Ensure your client supports OAuth authentication
+- Try the legacy Remote MCP configuration if OAuth isn't working
+- Check that you have the necessary permissions in your Sentry organization
+
+**Connection Issues**
+- Verify the MCP server URL is correct: `https://mcp.sentry.dev/mcp`
+- For legacy setups, use: `https://mcp.sentry.dev/sse`
+- Check your client's MCP configuration syntax
+
+**Missing Tools**
+- Ensure authentication completed successfully
+- Verify your Sentry organization access
+- Check for any error messages in your client's console
+
+For additional support, visit the [GitHub repository](https://github.com/getsentry/sentry-mcp) or contact Sentry support.