Skip to content

Commit b4aa648

Browse files
feat(MCP Docs) Codex + Warp docs (#14975)
Adds MCP setup guide for codex and warp --------- Co-authored-by: Alex Krawiec <[email protected]>
1 parent 7d8a0e4 commit b4aa648

File tree

1 file changed

+48
-18
lines changed

1 file changed

+48
-18
lines changed

docs/product/sentry-mcp/index.mdx

Lines changed: 48 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,10 @@ description: "Enable secure connectivity between Sentry issues and debugging dat
55
---
66

77
<Alert>
8-
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
9-
[GitHub](https://github.com/getsentry/sentry-mcp/issues) if you have any feedback or concerns.
8+
The Sentry MCP Server has been released for production, however MCP is a
9+
developing technology and changes should be expected. There will be bugs.
10+
Please reach out on [GitHub](https://github.com/getsentry/sentry-mcp/issues)
11+
if you have any feedback or concerns.
1012
</Alert>
1113

1214
## Overview
@@ -45,18 +47,21 @@ For clients that support OAuth, you can use the streamlined configuration that p
4547
```
4648

4749
This configuration:
50+
4851
- Enables OAuth authentication with your Sentry organization
4952
- Uses Streamable HTTP transport with automatic SSE fallback
5053
- Provides access to all 16+ available tools
5154
- Automatically handles authentication and session management
5255

5356
With OAuth configuration, you'll be prompted to:
57+
5458
1. Accept the OAuth authorization
5559
2. Login via your existing Sentry organization
5660
3. Grant access to the necessary permissions
5761

5862
<Alert>
59-
If you've joined a new Sentry organization, log out of your LLM's MCP integration and log back in to refresh access.
63+
If you've joined a new Sentry organization, log out of your LLM's MCP
64+
integration and log back in to refresh access.
6065
</Alert>
6166

6267
Once authenticated, you'll see the tools become available in your MCP client.
@@ -72,11 +77,7 @@ For clients that don't support OAuth, you can continue using the existing Remote
7277
"mcpServers": {
7378
"Sentry": {
7479
"command": "npx",
75-
"args": [
76-
"-y",
77-
"mcp-remote@latest",
78-
"https://mcp.sentry.dev/mcp"
79-
]
80+
"args": ["-y", "mcp-remote@latest", "https://mcp.sentry.dev/mcp"]
8081
}
8182
}
8283
}
@@ -87,6 +88,7 @@ For clients that don't support OAuth, you can continue using the existing Remote
8788
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.
8889

8990
To use STDIO mode, you'll need a Sentry User Auth Token with the following scopes:
91+
9092
- `org:read`
9193
- `project:read`
9294
- `project:write`
@@ -101,14 +103,15 @@ npx @sentry/mcp-server@latest --access-token=sentry-user-token --host=sentry.exa
101103
```
102104

103105
You can also use environment variables:
106+
104107
```bash
105108
SENTRY_ACCESS_TOKEN=your-token
106109
SENTRY_HOST=your-sentry-host
107110
```
108111

109112
### mcp.sentry.dev (live demo)
110113

111-
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.
114+
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.
112115

113116
![Sentry MCP live demo](./img/mcpdev.png)
114117

@@ -117,18 +120,21 @@ The [Sentry MCP page](https://mcp.sentry.dev) provides a simple way to configure
117120
The Sentry MCP Server provides comprehensive tools for interacting with Sentry data:
118121

119122
### Core Tools
123+
120124
- **Organizations**: List and query organization information
121125
- **Projects**: Find, list, and create projects
122126
- **Teams**: Manage and query team information
123127
- **Issues**: Access issue details, search, and analyze problems
124128
- **DSNs**: List and create Data Source Names for projects
125129

126130
### Analysis Tools
131+
127132
- **Error Searching**: Find errors in specific files or across projects
128133
- **Issue Analysis**: Detailed issue investigation with context
129134
- **Seer Integration**: Invoke Sentry's AI agent for root cause analysis and automated fixes
130135

131136
### Advanced Features
137+
132138
- **Release Management**: Query and analyze release information
133139
- **Performance Monitoring**: Access transaction and performance data
134140
- **Custom Queries**: Execute complex searches across Sentry data
@@ -147,41 +153,63 @@ Here are some example prompts you can use with the Sentry MCP:
147153

148154
![Sentry MCP using Autofix](./img/mcp-autofix1.png)
149155

150-
## Verified Clients
156+
## Verified Clients
151157

152-
The Sentry MCP Server has been verified to work in:
158+
The Sentry MCP Server has been verified to work in:
153159

154-
### Claude for Desktop
160+
### Claude for Desktop
155161

156162
Access developer tools via `CMD + ,``Developer``Edit Config` → edit the `claude_desktop_config.json` file
157163

158-
### Claude.ai
164+
### Claude.ai
159165

160166
Navigate to `Settings``Profile` → Scroll to `Integrations`, select `Add More`, and add the Sentry MCP server URL `https://mcp.sentry.dev/mcp`
161167

162-
### Claude Code
168+
### Claude Code
169+
170+
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`.
171+
172+
Once in, you'll be prompted to authenticate with OAuth to Sentry.
163173

164-
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`.
174+
### Codex
165175

166-
Once in, you'll be prompted to authenticate with OAuth to Sentry.
176+
From your CLI, enter `codex mcp add sentry -- npx -y mcp-remote@latest https://mcp.sentry.dev/mcp` and then access Codex with `codex`.
177+
178+
Once in, you'll be prompted to authenticate with Sentry using OAuth.
167179

168180
### Cursor
169181

170182
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.
171183

172-
You can still edit the `mcp.json` file manually if you prefer.
184+
You can still edit the `mcp.json` file manually if you prefer.
173185

174186
### VS Code and GitHub Copilot
175187

176188
Add the server using `CMD+Shift+P` and selecting `MCP: Add Server`
177189

190+
### Warp
191+
192+
Available via `Settings` -> `MCP Servers` -> `Manage MCP Servers` -> `Add MCP Server` -> `Sentry` -> `https://mcp.sentry.dev/mcp`.
193+
194+
```json
195+
{
196+
"Sentry": {
197+
"command": "npx",
198+
"args": ["-y", "mcp-remote@latest", "https://mcp.sentry.dev/mcp"],
199+
"env": {},
200+
"working_directory": null
201+
}
202+
}
203+
```
204+
178205
### Windsurf
179206

180207
Configure via the `Configure MCP` option in Cascade (CMD + L)
181208

182209
### Other Clients
183210

184211
The Sentry MCP Server follows standard MCP protocols and should work with any client that supports:
212+
185213
- OAuth authentication (recommended)
186214
- Remote MCP servers
187215
- SSE or Streamable HTTP transport
@@ -201,19 +229,21 @@ The Sentry MCP Server provides seamless integration with [Seer](/product/ai-in-s
201229
### Common Issues
202230

203231
**OAuth Authentication Problems**
232+
204233
- Ensure your client supports OAuth authentication
205234
- Try the legacy Remote MCP configuration if OAuth isn't working
206235
- Check that you have the necessary permissions in your Sentry organization
207236

208237
**Connection Issues**
238+
209239
- Verify the MCP server URL is correct: `https://mcp.sentry.dev/mcp`
210240
- For legacy setups, use: `https://mcp.sentry.dev/sse`
211241
- Check your client's MCP configuration syntax
212242

213243
**Missing Tools**
244+
214245
- Ensure authentication completed successfully
215246
- Verify your Sentry organization access
216247
- Check for any error messages in your client's console
217248

218249
For additional support, visit the [GitHub repository](https://github.com/getsentry/sentry-mcp) or contact Sentry support.
219-

0 commit comments

Comments
 (0)