From d145880cc9cf3042364d421d417cab73c3a0b03a Mon Sep 17 00:00:00 2001 From: Ogi <86684834+obostjancic@users.noreply.github.com> Date: Mon, 22 Sep 2025 23:49:45 +0200 Subject: [PATCH] chore(mcp-insights): remove beta callout --- docs/product/insights/ai/mcp/index.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/product/insights/ai/mcp/index.mdx b/docs/product/insights/ai/mcp/index.mdx index f509aa396c92a9..786d293f2089cc 100644 --- a/docs/product/insights/ai/mcp/index.mdx +++ b/docs/product/insights/ai/mcp/index.mdx @@ -4,8 +4,6 @@ sidebar_order: 20 description: "Learn how to use Sentry's MCP monitoring tools to trace and debug your Model Context Protocol implementations, including server connections, resource access, and tool executions." --- - - Sentry's MCP (Model Context Protocol) monitoring tools help you understand what's happening in your MCP implementations. They automatically collect information about MCP server connections, resource access, tool executions, and errors across your entire MCP pipeline—from client requests to server responses. ## Example MCP Monitoring Use Cases