diff --git a/docs/ai/dotagents.mdx b/docs/ai/dotagents.mdx index 370c626bd462f..8e94a4601335e 100644 --- a/docs/ai/dotagents.mdx +++ b/docs/ai/dotagents.mdx @@ -189,4 +189,4 @@ To gitignore managed skills instead (collaborators must run `install`), set `git - [dotagents on GitHub](https://github.com/getsentry/dotagents) - [Agent Skills](/ai/agent-skills/) -- [Sentry MCP Server](/ai/mcp/) +- [Sentry MCP Server](https://mcp.sentry.dev) diff --git a/docs/ai/img/mcp-tools.png b/docs/ai/img/mcp-tools.png deleted file mode 100644 index 9d37506ad9757..0000000000000 Binary files a/docs/ai/img/mcp-tools.png and /dev/null differ diff --git a/docs/ai/img/mcpdev.png b/docs/ai/img/mcpdev.png deleted file mode 100644 index d74c810f7d803..0000000000000 Binary files a/docs/ai/img/mcpdev.png and /dev/null differ diff --git a/docs/ai/index.mdx b/docs/ai/index.mdx index 831a94e0a7e97..2f559efd62508 100644 --- a/docs/ai/index.mdx +++ b/docs/ai/index.mdx @@ -31,7 +31,7 @@ keywords: className="w-full md:w-[calc(50%-12px)]" /> + ## AI In Sentry diff --git a/docs/ai/mcp.mdx b/docs/ai/mcp.mdx deleted file mode 100644 index 0fc009555f85a..0000000000000 --- a/docs/ai/mcp.mdx +++ /dev/null @@ -1,425 +0,0 @@ ---- -title: Sentry MCP Server -sidebar_order: 20 -description: >- - Connect your AI coding tools to Sentry using the Model Context Protocol (MCP) - for direct access to issues, errors, and debugging data. -keywords: - - MCP - - Model Context Protocol - - AI integration - - Claude - - Cursor - - debugging - - OAuth - - remote MCP - - Seer - - autofix -og_image: /og-images/ai-mcp.png ---- - - - The Sentry MCP Server is production-ready, but MCP is still evolving. Expect - rough edges. File bugs on - [GitHub](https://github.com/getsentry/sentry-mcp/issues). - - -The [Sentry MCP Server](https://mcp.sentry.dev) connects your AI coding tools to Sentry using the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction). It gives your agent direct access to issues, errors, projects, and [Seer](/product/ai-in-sentry/seer/) analysis. - -## Setup - -Sentry hosts the MCP server at `https://mcp.sentry.dev/mcp`. Your client connects over Streamable HTTP with OAuth — there's nothing to install. - -Add the server automatically: - -```bash -npx add-mcp https://mcp.sentry.dev/mcp -``` - -Or add it manually to your client's MCP configuration: - -```json -{ - "mcpServers": { - "sentry": { - "url": "https://mcp.sentry.dev/mcp" - } - } -} -``` - -When you first connect, you'll be prompted to log in with your Sentry organization and grant access. During authentication, you select which tool groups to expose — this keeps the context window focused on the tools you actually need. - -The Cloud transport requires your client to support OAuth and Streamable HTTP. All clients listed under [Client Instructions](#client-instructions) support this natively — if yours doesn't, use the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge or the [Stdio Transport](#stdio-transport) instead. - -![Available Sentry MCP Tools](./img/mcp-tools.png) - -See [Client Instructions](#client-instructions) for setup steps specific to your editor or IDE. - - - If you've joined a new Sentry organization, log out of your LLM's MCP - integration and log back in to refresh access. - - -### Stdio Transport - -Alternatively, you can run the MCP server locally via `npx @sentry/mcp-server`. Your IDE spawns the process and communicates over stdin/stdout. This is required for [self-hosted Sentry](#self-hosted-sentry). - -For sentry.io users, the server uses **device-code authentication**. On first run it opens your browser to log in — no manual token creation needed. The token is cached at `~/.sentry/mcp.json` for future sessions. - -If you're in a non-interactive environment (CI, piped stdio), authenticate ahead of time: - -```bash -npx @sentry/mcp-server@latest auth login -``` - -You can check or clear your auth state with `auth status` and `auth logout`. - -Add the server to your client's MCP configuration: - -```json -{ - "mcpServers": { - "sentry": { - "command": "npx", - "args": ["@sentry/mcp-server@latest"] - } - } -} -``` - - - When using stdio, the AI-powered search tools (`search_events`, - `search_issues`) require an `OPENAI_API_KEY` environment variable for natural - language query translation. The Cloud transport handles this automatically. - - -## Configuration - -### Scope to an Organization or Project - -Restrict the MCP session to a specific organization or project to keep context focused. - -**Cloud:** Append the slug to the URL path: - -- `https://mcp.sentry.dev/mcp/my-org` — one organization -- `https://mcp.sentry.dev/mcp/my-org/my-project` — one project - -**Stdio:** Use CLI flags: - -- `--organization-slug=my-org` -- `--project-slug=my-project` - -When scoped, redundant discovery tools are hidden automatically. - -## Self-Hosted Sentry - -Self-hosted instances use the stdio transport with an access token. The Cloud endpoint and device-code OAuth are only available for sentry.io. - -Create a token in **User Settings → Auth Tokens** with these scopes: - -- `org:read` -- `project:read` -- `project:write` -- `team:read` -- `team:write` -- `event:write` - -Configure the server with your hostname: - -```bash -npx @sentry/mcp-server@latest --access-token=YOUR_TOKEN --host=sentry.example.com -``` - -Or as environment variables: - -```bash -SENTRY_ACCESS_TOKEN=YOUR_TOKEN -SENTRY_HOST=sentry.example.com -``` - -JSON config for clients that support it: - -```json -{ - "mcpServers": { - "sentry": { - "command": "npx", - "args": [ - "@sentry/mcp-server@latest", - "--access-token=YOUR_TOKEN", - "--host=sentry.example.com" - ] - } - } -} -``` - -Some cloud-only features like Seer aren't available on self-hosted. Disable them: - -```bash -npx @sentry/mcp-server@latest --access-token=YOUR_TOKEN --host=sentry.example.com --disable-skills=seer -``` - - - The MCP server targets the cloud service. Some tools may call APIs that aren't - available in your self-hosted version yet. - - -## Common Workflows - -### Debug an Issue from a Link - -Paste a Sentry issue URL into your agent. The MCP server pulls the stack trace, event details, and tags so the agent can investigate and propose a fix. Try prompts like: - -- "Fix this issue: `https://sentry.io/issues/6811213890/`" -- "What's the root cause of `https://my-org.sentry.io/issues/PROJECT-123/`?" - -### Analyze Incidents with Search - -Ask questions in plain English. The `search_issues` and `search_events` tools translate your queries into Sentry's search syntax: - -- "What are the top unresolved errors in production this week?" -- "Show me errors that started after the last deploy." -- "Compare error rates between v2.3 and v2.4 for my-project." - -## Client Instructions - -Setup steps for specific editors and IDEs. All instructions default to the Cloud transport — see [Stdio Transport](#stdio-transport) if you need the local server. - -### Claude Code - - - -```bash -claude mcp add --transport http sentry https://mcp.sentry.dev/mcp -``` - -Launch Claude Code with `claude`. You'll be prompted to authenticate via OAuth. - - - -### Cursor - - - -Go to `Cursor` → `Settings` → `Cursor Settings` → `MCP` and add the Sentry MCP server. Cursor 1.0+ supports OAuth and Streamable HTTP natively. - -You can also edit your `mcp.json` directly: - -```json -{ - "mcpServers": { - "sentry": { - "url": "https://mcp.sentry.dev/mcp" - } - } -} -``` - - - -### Claude for Desktop - - - -Open `CMD + ,` → `Developer` → `Edit Config`, then add to `claude_desktop_config.json`: - -```json -{ - "mcpServers": { - "sentry": { - "url": "https://mcp.sentry.dev/mcp" - } - } -} -``` - -Restart Claude Desktop to pick up the changes. - - - -### Claude.ai - - - -Go to `Settings` → `Profile` → `Integrations` → `Add More`, and add: - -``` -https://mcp.sentry.dev/mcp -``` - - - -### VS Code and GitHub Copilot - - - -Open the Command Palette (`CMD+Shift+P`) → `MCP: Add Server` and enter: - -``` -https://mcp.sentry.dev/mcp -``` - - - -### Codex - - - -```bash -codex mcp add sentry --url https://mcp.sentry.dev/mcp -``` - -Launch Codex with `codex`. You'll be prompted to authenticate via OAuth. - - - -### Windsurf - - - -Open Cascade (`CMD + L`) → `Configure MCP` and add: - -``` -https://mcp.sentry.dev/mcp -``` - - - -### Warp - - - -Go to `Settings` → `MCP Servers` → `+ Add` → **Streamable HTTP or SSE Server (URL)**: - -```json -{ - "sentry": { - "url": "https://mcp.sentry.dev/mcp" - } -} -``` - - - -### Amp - - - -**VS Code Extension** — update `settings.json`: - -```json -"amp.mcpServers": { - "sentry": { - "url": "https://mcp.sentry.dev/mcp" - } -} -``` - -**CLI:** - -```bash -amp mcp add sentry --url https://mcp.sentry.dev/mcp -``` - - - -### Factory Droid - - - -Open the MCP menu with `/mcp` → `Add MCP Server from Registry` → search for `sentry`. - - - -### Vercel v0 - - - -In the [v0.app](https://v0.app) UI: `Account Settings` → `Integrations` → under **MCP Connections** click `Add MCP` → search for Sentry. - - - -### OpenCode - - - -Add to your `opencode.jsonc`: - -```json -{ - "$schema": "https://opencode.ai/config.json", - "mcp": { - "sentry": { - "type": "remote", - "url": "https://mcp.sentry.dev/mcp", - "oauth": {} - } - } -} -``` - -Then authenticate: - -```bash -opencode mcp auth sentry -``` - - - -### Other Clients - - - -The Sentry MCP Server works with any client that supports **OAuth** and **Streamable HTTP** (with SSE fallback). Use `https://mcp.sentry.dev/mcp` in your client's config. - -If your client doesn't support OAuth or Streamable HTTP yet, use the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge as a workaround. - - - -### Test the Connection - -The [Sentry MCP page](https://mcp.sentry.dev) has a web interface where you can authenticate and test the server directly in your browser. - -![Sentry MCP live demo](./img/mcpdev.png) - - - -## Troubleshooting - -**OAuth Authentication Problems** - -- Ensure your client supports OAuth and Streamable HTTP — if it doesn't, use the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge or the [Stdio Transport](#stdio-transport) -- Check that you have the right permissions in your Sentry organization -- Verify the URL is exactly `https://mcp.sentry.dev/mcp` -- Try reauthenticating (see below) - -**Reauthenticating in Claude Code** - -1. Type `/mcp` in the Claude Code prompt -2. Select the **sentry** server -3. Choose **"Clear authentication"** or **"Authenticate"** to re-trigger OAuth - -**Reauthenticating in OpenCode** - -1. `opencode mcp auth list` — check status -2. `opencode mcp logout sentry` — log out -3. `opencode mcp auth sentry` — log back in - -**Reauthenticating in Factory Droid** - -1. Type `/mcp` → select **sentry** → **"Reauthenticate"** - -**Connection Issues** - -- Verify the URL: `https://mcp.sentry.dev/mcp` -- Check your client's MCP config syntax - -**Missing Tools** - -- Verify authentication completed -- Check your Sentry org access -- Look for errors in your client's console - -For additional help, visit the [GitHub repository](https://github.com/getsentry/sentry-mcp) or contact Sentry support. diff --git a/docs/ai/sentry-cli.mdx b/docs/ai/sentry-cli.mdx deleted file mode 100644 index 25bc9cabd6fac..0000000000000 --- a/docs/ai/sentry-cli.mdx +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Sentry CLI -sidebar_order: 25 -new: true -description: "A natural-language CLI for developers and AI agents. Investigate issues, use Seer's Autofix, and manage Sentry projects from your terminal." -keywords: - - CLI - - Sentry CLI - - terminal - - command line - - AI agent - - Seer - - issue debugging - - agentic ---- - -The [Sentry CLI](https://cli.sentry.dev) is a command-line tool built for developers and AI agents. It auto-detects your project from `.env` files and the local codebase, so you don't need config files or flags. Type natural commands, investigate issues, use [Seer's Autofix](/product/ai-in-sentry/seer/autofix/), and manage your Sentry projects directly from the terminal. - -For full documentation, visit [cli.sentry.dev](https://cli.sentry.dev). - -## Installation - -Install the CLI using the install script: - -```bash -curl https://cli.sentry.dev/install -fsS | bash -``` - -Or install globally with a package manager: - -```bash {tabTitle: npm} -npm install -g sentry -``` - -```bash {tabTitle: pnpm} -pnpm add -g sentry -``` - -```bash {tabTitle: yarn} -yarn global add sentry -``` - -```bash {tabTitle: bun} -bun add -g sentry -``` - -You can also run it directly without installing: - -```bash {tabTitle: npx} -npx sentry --help -``` - -```bash {tabTitle: pnpm dlx} -pnpm dlx sentry --help -``` - -## Authentication - -Authenticate using the OAuth device flow: - -```bash -sentry auth login -``` - -You'll receive a URL and code to enter in your browser. Once authorized, the CLI stores your credentials automatically. - -You can also authenticate with an API token directly: - -```bash -sentry auth login --token YOUR_SENTRY_API_TOKEN -``` - -Create API tokens in your [Sentry account settings](https://sentry.io/settings/account/api/auth-tokens/). - -## Key Commands - -The CLI auto-detects your project context, so most commands work without specifying a project or organization. For a complete list of available commands, see the [commands reference](https://cli.sentry.dev/commands/). - -### List Issues - -```bash -sentry issue list -``` - -### Investigate an Issue - -Use Seer's Autofix to analyze an issue: - -```bash -sentry issue explain -``` - -### Get a Fix Plan - -Generate a step-by-step fix you can apply: - -```bash -sentry issue plan -``` - -### Browse Projects and Organizations - -```bash -sentry project list -sentry org list -``` - -### Structured Output - -Every command supports JSON output for scripting and pipelines: - -```bash -sentry org list --json | jq '.[0]' -``` - -## Agentic Usage - -AI coding agents like Claude Code can use the Sentry CLI through the agent skill system. This allows agents to list issues, inspect events, and interact with Sentry from your development environment. - -Add the Sentry CLI skill to your agent: - -```bash -npx skills add https://cli.sentry.dev -``` - -The agent uses your existing CLI authentication, so run `sentry auth login` first. - -For more details on agentic usage, see the [Agentic Usage guide on cli.sentry.dev](https://cli.sentry.dev/agentic-usage). - -## Next Steps - -- [Full CLI documentation](https://cli.sentry.dev/getting-started/) — installation, authentication, and configuration details -- [Commands reference](https://cli.sentry.dev/commands/) — complete list of available commands -- [Agentic usage](https://cli.sentry.dev/agentic-usage) — using the CLI with AI coding agents -- [GitHub repository](https://github.com/getsentry/cli) — source code and issue tracker diff --git a/docs/product/explore/logs/index.mdx b/docs/product/explore/logs/index.mdx index 4b1c9a1f3fca9..19bd1129935fe 100644 --- a/docs/product/explore/logs/index.mdx +++ b/docs/product/explore/logs/index.mdx @@ -126,7 +126,7 @@ Learn more about [Alerts](/product/monitors-and-alerts/alerts/) and [custom dash Your Sentry logs can be leveraged with AI agents and tooling for debugging, summarizing, and automated analysis. - **[Sentry CLI](/cli/logs/)**: Provides command-line access to your logs, making it easy to feed log data directly into AI tools and scripts for analysis. -- **[Sentry MCP Server](/ai/mcp/)**: Provides secure connectivity between your Sentry data and LLM clients using the Model Context Protocol. This enables natural language queries and deep integration with AI tools like Claude, Cursor, and VS Code. +- **[Sentry MCP Server](https://mcp.sentry.dev)**: Provides secure connectivity between your Sentry data and LLM clients using the Model Context Protocol. This enables natural language queries and deep integration with AI tools like Claude, Cursor, and VS Code. - **[Seer](/product/ai-in-sentry/seer/)**: Sentry's AI debugging agent automatically uses logs alongside other telemetry data to provide intelligent issue analysis and automated fixes. ## Video - Getting Started with Sentry Logs diff --git a/docs/product/explore/metrics/index.mdx b/docs/product/explore/metrics/index.mdx index 4e040b244c683..06a8f32b4f838 100644 --- a/docs/product/explore/metrics/index.mdx +++ b/docs/product/explore/metrics/index.mdx @@ -198,5 +198,5 @@ Application Metrics are best for **application and code-based health signals**, Your Sentry metrics can be leveraged with AI agents and tooling for debugging and automated analysis: -- **[Sentry MCP Server](/ai/mcp/)**: Enables natural language queries and deep integration with AI tools like Claude, Cursor, and VS Code using the Model Context Protocol +- **[Sentry MCP Server](https://mcp.sentry.dev)**: Enables natural language queries and deep integration with AI tools like Claude, Cursor, and VS Code using the Model Context Protocol - **[Seer](/product/ai-in-sentry/seer/)**: Sentry's AI debugging agent can use metrics alongside traces, logs, and errors to provide intelligent issue analysis diff --git a/middleware.ts b/middleware.ts index e68a37151f724..a5df28b049830 100644 --- a/middleware.ts +++ b/middleware.ts @@ -3436,7 +3436,7 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ }, { from: '/product/sentry-mcp/', - to: '/ai/mcp/', + to: 'https://mcp.sentry.dev', }, { from: '/product/metrics/', diff --git a/public/ai/img/IconShield.svg b/public/ai/img/IconShield.svg new file mode 100644 index 0000000000000..317edb43ff88c --- /dev/null +++ b/public/ai/img/IconShield.svg @@ -0,0 +1,3 @@ + + + diff --git a/redirects.js b/redirects.js index e457d01568a37..08f54bbfe0ee1 100644 --- a/redirects.js +++ b/redirects.js @@ -1776,6 +1776,15 @@ const userDocsRedirects = [ '/platforms/react-native/data-management/debug-files/source-context/data-management/debug-files/upload/', destination: '/platforms/react-native/data-management/debug-files/upload/', }, + // Redirect MCP and CLI pages to their dedicated sites + { + source: '/ai/mcp/', + destination: 'https://mcp.sentry.dev', + }, + { + source: '/ai/sentry-cli/', + destination: 'https://cli.sentry.dev', + }, // Redirects for Insights → Sentry Dashboards migration { source: '/product/insights/llm-monitoring/:path*', diff --git a/src/components/home.tsx b/src/components/home.tsx index 4a3fa5fb59a65..4f9b858aa6782 100644 --- a/src/components/home.tsx +++ b/src/components/home.tsx @@ -336,7 +336,12 @@ export async function Home() { Skills {' '} and{' '} - + MCP server {' '} with your agents. Debug agents and MCP servers by{' '} diff --git a/src/components/linkCard.tsx b/src/components/linkCard.tsx index dec28a66f1a1b..c4aa69ed68218 100644 --- a/src/components/linkCard.tsx +++ b/src/components/linkCard.tsx @@ -15,8 +15,14 @@ export function LinkCard({ icon?: string; iconSrc?: string; }) { + const isExternal = href.includes('://'); + const Wrapper = isExternal ? 'a' : Link; + const externalProps = isExternal + ? {target: '_blank' as const, rel: 'noopener noreferrer'} + : {}; + return ( - +
@@ -35,7 +41,7 @@ export function LinkCard({

{description}

- + ); } diff --git a/src/components/sidebar/dynamicNav.tsx b/src/components/sidebar/dynamicNav.tsx index f8262d50c10b6..c966b5a69079c 100644 --- a/src/components/sidebar/dynamicNav.tsx +++ b/src/components/sidebar/dynamicNav.tsx @@ -6,6 +6,7 @@ import {getUnversionedPath, VERSION_INDICATOR} from 'sentry-docs/versioning'; import {CollapsibleSidebarLink} from './collapsibleSidebarLink'; import {SidebarLink, SidebarSeparator} from './sidebarLink'; +import type {ExternalSidebarLink} from './types'; // Section configuration for sidebar organization const SECTION_LABELS: Record = { @@ -259,6 +260,7 @@ type Props = { tree: EntityTree[]; collapsible?: boolean; exclude?: string[]; + extraLinks?: ExternalSidebarLink[]; title?: string; }; @@ -268,6 +270,7 @@ export function DynamicNav({ tree, collapsible = false, exclude = [], + extraLinks, }: Props) { if (root.startsWith('/')) { root = root.substring(1); @@ -340,7 +343,25 @@ export function DynamicNav({ )} ({ + name: link.href, + node: { + path: link.href, + context: { + title: link.title, + sidebar_order: link.order, + draft: false, + }, + }, + children: [], + })), + ] + : entity.children + } exclude={exclude} showDepth={0} path={linkPath} diff --git a/src/components/sidebar/productSidebar.tsx b/src/components/sidebar/productSidebar.tsx index d392e63efc59d..35677093cf6c1 100644 --- a/src/components/sidebar/productSidebar.tsx +++ b/src/components/sidebar/productSidebar.tsx @@ -4,7 +4,7 @@ import {DynamicNav, toTree} from './dynamicNav'; import {NavNode, ProductSidebarProps} from './types'; import {docNodeToNavNode, getNavNodes} from './utils'; -export function ProductSidebar({rootNode, items}: ProductSidebarProps) { +export function ProductSidebar({rootNode, items, extraLinks}: ProductSidebarProps) { const itemTree = (item: string) => { const node = nodeForPath(rootNode, item); if (!node) { @@ -26,12 +26,12 @@ export function ProductSidebar({rootNode, items}: ProductSidebarProps) { title={item.title} tree={tree} collapsible={false} + extraLinks={extraLinks} /> ) ); })} - {/* External links menu removed from here */} ); } diff --git a/src/components/sidebar/sidebarNavigation.tsx b/src/components/sidebar/sidebarNavigation.tsx index 15e58a4fa8f17..6db0452bff65f 100644 --- a/src/components/sidebar/sidebarNavigation.tsx +++ b/src/components/sidebar/sidebarNavigation.tsx @@ -24,6 +24,11 @@ export async function SidebarNavigation({path}: {path: string[]}) { ); } diff --git a/src/components/sidebar/types.ts b/src/components/sidebar/types.ts index b5b87c824db40..c383b91804680 100644 --- a/src/components/sidebar/types.ts +++ b/src/components/sidebar/types.ts @@ -17,9 +17,16 @@ export type DefaultSidebarProps = SidebarProps & { path: string[]; }; +export type ExternalSidebarLink = { + href: string; + order: number; + title: string; +}; + export type ProductSidebarProps = { items: {root: string; title: string}[]; rootNode: DocNode; + extraLinks?: ExternalSidebarLink[]; }; export type PlatformSidebarProps = {