From 10a606d6c5cf1685dbe88937ee37c95958bb7564 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Tue, 20 Oct 2026 12:36:53 +0000 Subject: [PATCH 1/3] docs(js): Document `dataCollection.mcp` option MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Jan Peer Stöcklmair --- .../common/configuration/options.mdx | 3 ++- .../data-management/data-collected/index.mdx | 26 +++++++++++++++++-- .../common/mcp-monitoring/index.mdx | 8 +++--- .../common/migration/v10-to-v11/index.mdx | 2 ++ docs/product/mcp-servers/getting-started.mdx | 4 +-- .../javascript-v11/data-collection.mdx | 2 ++ 6 files changed, 37 insertions(+), 8 deletions(-) diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx index 37153b6370c624..7d30453a90ac18 100644 --- a/docs/platforms/javascript/common/configuration/options.mdx +++ b/docs/platforms/javascript/common/configuration/options.mdx @@ -137,7 +137,8 @@ For more on what data Sentry collects and how to control it, see
`variables`: Collect the variables that are passed to GraphQL operations.

The operation name and type are always collected. | -| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values. | +| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values.

Content from instrumented MCP servers is controlled by `mcp`, not `genAI`. | +| `mcp` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of incoming MCP requests: tool call arguments, prompt arguments, and the message payload of logging notifications.

`outputs`: Collect the content of MCP responses, such as tool results and prompt messages.

Metadata, such as the method name, tool or prompt name, session, protocol version, content counts, and error status, is always collected. The `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` take precedence over these values. Requires SDK version `11.9.0` or newer. In earlier versions, `genAI` controls MCP content. | | `databaseQueryData` | `boolean` | `true` | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data.

The sanitized or parameterized query text (`db.query.text`) is **not** controlled by this option. Structural metadata, such as the database system, query summary, operation name, and table, is also **always** collected. | | `queues` | `boolean` | `true` | Collect the arguments passed to tasks within queues. For Kafka, this is the message key. Structural metadata, such as the messaging system, the destination name, and the operation, is always collected. | | `stackFrameVariables` | `CollectBehavior` | `true` | Capture local variable values in stack frames. Allow/deny lists match variable names. | diff --git a/docs/platforms/javascript/common/data-management/data-collected/index.mdx b/docs/platforms/javascript/common/data-management/data-collected/index.mdx index aee6cfbef1c6f5..e0bde1005ad943 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -272,8 +272,6 @@ Sentry.init({ The content of generative AI inputs (system instructions, prompt messages, tool definitions, and tool call arguments) and outputs (such as completion text and tool call results) might carry personal data. By default, the SDK records both inputs and outputs. Metadata like model ID and token counts is always collected. - The same setting applies to instrumented MCP servers. By default, the SDK records the inputs and outputs of tool calls, prompt retrievals, and resource reads. Use the `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` to control recording per server. - Use the `dataCollection.genAI` option to control this. For example, opt out of recording AI message content while keeping the metadata: ```JavaScript @@ -287,6 +285,30 @@ Sentry.init({ }, }); ``` + + ## MCP Requests And Responses + + When you instrument an MCP server, the SDK always sends metadata like the method name, the tool or prompt name, the session, and the error status. + + The content of MCP requests (tool call arguments, prompt arguments, and logging notification payloads) and responses (tool results and prompt messages) might carry personal data or secrets. By default, the SDK records both. + + Use the `dataCollection.mcp` option to control this. It's independent of `dataCollection.genAI`. For example, opt out of recording MCP content while keeping the metadata: + + ```JavaScript + Sentry.init({ + dsn: "___PUBLIC_DSN___", + dataCollection: { + mcp: { + inputs: false, + outputs: false, + }, + }, + }); + ``` + + To control recording for a single server, use the `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry`. They take precedence over `dataCollection.mcp`. + + The `dataCollection.mcp` option requires SDK version `11.9.0` or newer. In earlier versions, `dataCollection.genAI` controls MCP content. diff --git a/docs/platforms/javascript/common/mcp-monitoring/index.mdx b/docs/platforms/javascript/common/mcp-monitoring/index.mdx index 69cf07ee99ed37..edcbc334fb9894 100644 --- a/docs/platforms/javascript/common/mcp-monitoring/index.mdx +++ b/docs/platforms/javascript/common/mcp-monitoring/index.mdx @@ -24,18 +24,20 @@ Support for `@modelcontextprotocol/server` 2.x requires Sentry JavaScript SDK ve By default, the SDK sends the inputs and outputs of your MCP tool calls, prompt retrievals, and resource reads. This gives you rich debugging context. MCP payloads can carry sensitive data, such as tokens, file paths, or private user content. Review what your server handles before you deploy to production. -The `dataCollection.genAI` option controls this recording globally for both MCP and AI instrumentation: +The `dataCollection.mcp` option controls this recording globally for all MCP servers. `inputs` covers tool call arguments, prompt arguments, and logging notification payloads. `outputs` covers tool results and prompt messages. Metadata, such as the tool name, session, and error status, is always collected: ```javascript Sentry.init({ dsn: "___PUBLIC_DSN___", dataCollection: { - genAI: { inputs: false, outputs: false }, + mcp: { inputs: false, outputs: false }, }, }); ``` -To control recording for a specific server, pass it to `wrapMcpServerWithSentry` with the `recordInputs` and `recordOutputs` options. These options override the `dataCollection.genAI` settings, and they also apply to a server the SDK has already instrumented automatically: +The `dataCollection.mcp` option requires Sentry JavaScript SDK version `11.9.0` or newer. In earlier versions, `dataCollection.genAI` controls MCP recording together with AI instrumentation. Starting with `11.9.0`, `genAI` no longer affects MCP servers, so if you used `genAI` to turn off MCP recording, set `mcp` as well. + +To control recording for a specific server, pass it to `wrapMcpServerWithSentry` with the `recordInputs` and `recordOutputs` options. These options override the `dataCollection.mcp` settings, and they also apply to a server the SDK has already instrumented automatically: ```javascript const server = Sentry.wrapMcpServerWithSentry(mcpServer, { diff --git a/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx b/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx index 036dcba0130494..c20cfdd1258e72 100644 --- a/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx +++ b/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx @@ -172,6 +172,8 @@ Sentry.init({ httpBodies: [], urlQueryParams: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, genAI: { inputs: false, outputs: false }, + // Requires SDK 11.9.0 or newer. Earlier versions use `genAI` for MCP content. + mcp: { inputs: false, outputs: false }, databaseQueryData: false, graphQL: { document: false, variables: false }, }, diff --git a/docs/product/mcp-servers/getting-started.mdx b/docs/product/mcp-servers/getting-started.mdx index c973a4514bf2dd..e7bddd7b1d12f4 100644 --- a/docs/product/mcp-servers/getting-started.mdx +++ b/docs/product/mcp-servers/getting-started.mdx @@ -62,7 +62,7 @@ _Type: `boolean`_ Records inputs to MCP tool and prompt calls (such as tool arguments and prompt parameters). -Defaults to `dataCollection.genAI.inputs`. In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. +Defaults to `dataCollection.mcp.inputs` (`dataCollection.genAI.inputs` before Sentry JavaScript SDK `11.9.0`). In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. ##### `recordOutputs` @@ -70,7 +70,7 @@ _Type: `boolean`_ Records outputs from MCP tool and prompt calls (such as tool results and prompt messages). -Defaults to `dataCollection.genAI.outputs`. In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. +Defaults to `dataCollection.mcp.outputs` (`dataCollection.genAI.outputs` before Sentry JavaScript SDK `11.9.0`). In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. #### Cloudflare Workers diff --git a/includes/migration/javascript-v11/data-collection.mdx b/includes/migration/javascript-v11/data-collection.mdx index 3b86c84c2539d5..02971a128b4739 100644 --- a/includes/migration/javascript-v11/data-collection.mdx +++ b/includes/migration/javascript-v11/data-collection.mdx @@ -49,6 +49,8 @@ Sentry.init({ httpBodies: [], urlQueryParams: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, genAI: { inputs: false, outputs: false }, + // Requires SDK 11.9.0 or newer. Earlier versions use `genAI` for MCP content. + mcp: { inputs: false, outputs: false }, databaseQueryData: false, graphQL: { document: false, variables: false }, }, From 4c0a07e11358a341cbd0c9ca948f712f31c99941 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Tue, 20 Oct 2026 12:50:03 +0000 Subject: [PATCH 2/3] docs(js): Document the genAI fallback for dataCollection.mcp MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Jan Peer Stöcklmair --- docs/platforms/javascript/common/configuration/options.mdx | 4 ++-- .../common/data-management/data-collected/index.mdx | 2 +- docs/platforms/javascript/common/mcp-monitoring/index.mdx | 2 +- .../javascript/common/migration/v10-to-v11/index.mdx | 2 -- docs/product/mcp-servers/getting-started.mdx | 4 ++-- includes/migration/javascript-v11/data-collection.mdx | 2 -- 6 files changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx index 7d30453a90ac18..a53c4f73adb378 100644 --- a/docs/platforms/javascript/common/configuration/options.mdx +++ b/docs/platforms/javascript/common/configuration/options.mdx @@ -137,8 +137,8 @@ For more on what data Sentry collects and how to control it, see
`variables`: Collect the variables that are passed to GraphQL operations.

The operation name and type are always collected. | -| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values.

Content from instrumented MCP servers is controlled by `mcp`, not `genAI`. | -| `mcp` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of incoming MCP requests: tool call arguments, prompt arguments, and the message payload of logging notifications.

`outputs`: Collect the content of MCP responses, such as tool results and prompt messages.

Metadata, such as the method name, tool or prompt name, session, protocol version, content counts, and error status, is always collected. The `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` take precedence over these values. Requires SDK version `11.9.0` or newer. In earlier versions, `genAI` controls MCP content. | +| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values.

For instrumented MCP servers, `mcp` takes precedence over these values. | +| `mcp` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of incoming MCP requests: tool call arguments, prompt arguments, and the message payload of logging notifications.

`outputs`: Collect the content of MCP responses, such as tool results and prompt messages.

Metadata, such as the method name, tool or prompt name, session, protocol version, content counts, and error status, is always collected. The `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` take precedence over these values. If you don't set a field, MCP servers use the matching `genAI` field. Requires SDK version `11.9.0` or newer. In earlier versions, only `genAI` controls MCP content. | | `databaseQueryData` | `boolean` | `true` | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data.

The sanitized or parameterized query text (`db.query.text`) is **not** controlled by this option. Structural metadata, such as the database system, query summary, operation name, and table, is also **always** collected. | | `queues` | `boolean` | `true` | Collect the arguments passed to tasks within queues. For Kafka, this is the message key. Structural metadata, such as the messaging system, the destination name, and the operation, is always collected. | | `stackFrameVariables` | `CollectBehavior` | `true` | Capture local variable values in stack frames. Allow/deny lists match variable names. | diff --git a/docs/platforms/javascript/common/data-management/data-collected/index.mdx b/docs/platforms/javascript/common/data-management/data-collected/index.mdx index e0bde1005ad943..94f5e90e247c7e 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -292,7 +292,7 @@ Sentry.init({ The content of MCP requests (tool call arguments, prompt arguments, and logging notification payloads) and responses (tool results and prompt messages) might carry personal data or secrets. By default, the SDK records both. - Use the `dataCollection.mcp` option to control this. It's independent of `dataCollection.genAI`. For example, opt out of recording MCP content while keeping the metadata: + Use the `dataCollection.mcp` option to control this. It takes precedence over `dataCollection.genAI`. If you don't set it, MCP servers follow your `genAI` settings. For example, opt out of recording MCP content while keeping the metadata: ```JavaScript Sentry.init({ diff --git a/docs/platforms/javascript/common/mcp-monitoring/index.mdx b/docs/platforms/javascript/common/mcp-monitoring/index.mdx index edcbc334fb9894..befc506f215416 100644 --- a/docs/platforms/javascript/common/mcp-monitoring/index.mdx +++ b/docs/platforms/javascript/common/mcp-monitoring/index.mdx @@ -35,7 +35,7 @@ Sentry.init({ }); ``` -The `dataCollection.mcp` option requires Sentry JavaScript SDK version `11.9.0` or newer. In earlier versions, `dataCollection.genAI` controls MCP recording together with AI instrumentation. Starting with `11.9.0`, `genAI` no longer affects MCP servers, so if you used `genAI` to turn off MCP recording, set `mcp` as well. +The `dataCollection.mcp` option requires Sentry JavaScript SDK version `11.9.0` or newer. In earlier versions, `dataCollection.genAI` controls MCP recording together with AI instrumentation. If you don't set `mcp`, the SDK falls back to the matching `genAI` field, so existing `genAI` settings keep applying to MCP servers. When you set both, `mcp` takes precedence. To control recording for a specific server, pass it to `wrapMcpServerWithSentry` with the `recordInputs` and `recordOutputs` options. These options override the `dataCollection.mcp` settings, and they also apply to a server the SDK has already instrumented automatically: diff --git a/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx b/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx index c20cfdd1258e72..036dcba0130494 100644 --- a/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx +++ b/docs/platforms/javascript/common/migration/v10-to-v11/index.mdx @@ -172,8 +172,6 @@ Sentry.init({ httpBodies: [], urlQueryParams: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, genAI: { inputs: false, outputs: false }, - // Requires SDK 11.9.0 or newer. Earlier versions use `genAI` for MCP content. - mcp: { inputs: false, outputs: false }, databaseQueryData: false, graphQL: { document: false, variables: false }, }, diff --git a/docs/product/mcp-servers/getting-started.mdx b/docs/product/mcp-servers/getting-started.mdx index e7bddd7b1d12f4..94bb7927e437f2 100644 --- a/docs/product/mcp-servers/getting-started.mdx +++ b/docs/product/mcp-servers/getting-started.mdx @@ -62,7 +62,7 @@ _Type: `boolean`_ Records inputs to MCP tool and prompt calls (such as tool arguments and prompt parameters). -Defaults to `dataCollection.mcp.inputs` (`dataCollection.genAI.inputs` before Sentry JavaScript SDK `11.9.0`). In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. +Defaults to `dataCollection.mcp.inputs`, then `dataCollection.genAI.inputs`. Before Sentry JavaScript SDK `11.9.0`, only `dataCollection.genAI.inputs` applies. In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. ##### `recordOutputs` @@ -70,7 +70,7 @@ _Type: `boolean`_ Records outputs from MCP tool and prompt calls (such as tool results and prompt messages). -Defaults to `dataCollection.mcp.outputs` (`dataCollection.genAI.outputs` before Sentry JavaScript SDK `11.9.0`). In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. +Defaults to `dataCollection.mcp.outputs`, then `dataCollection.genAI.outputs`. Before Sentry JavaScript SDK `11.9.0`, only `dataCollection.genAI.outputs` applies. In Sentry JavaScript SDK 10.x, when `dataCollection` isn't configured, this follows `sendDefaultPii`. #### Cloudflare Workers diff --git a/includes/migration/javascript-v11/data-collection.mdx b/includes/migration/javascript-v11/data-collection.mdx index 02971a128b4739..3b86c84c2539d5 100644 --- a/includes/migration/javascript-v11/data-collection.mdx +++ b/includes/migration/javascript-v11/data-collection.mdx @@ -49,8 +49,6 @@ Sentry.init({ httpBodies: [], urlQueryParams: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, genAI: { inputs: false, outputs: false }, - // Requires SDK 11.9.0 or newer. Earlier versions use `genAI` for MCP content. - mcp: { inputs: false, outputs: false }, databaseQueryData: false, graphQL: { document: false, variables: false }, }, From 835c4d8a59b322c28b22c8509af82a64e03956b6 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Wed, 21 Oct 2026 08:40:33 +0000 Subject: [PATCH 3/3] docs(js): Link wrapMcpServerWithSentry to its options MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Jan VamPeer Stöcklmair --- docs/platforms/javascript/common/configuration/options.mdx | 2 +- .../common/data-management/data-collected/index.mdx | 6 +++++- docs/product/mcp-servers/getting-started.mdx | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx index a53c4f73adb378..d6473f15871256 100644 --- a/docs/platforms/javascript/common/configuration/options.mdx +++ b/docs/platforms/javascript/common/configuration/options.mdx @@ -138,7 +138,7 @@ For more on what data Sentry collects and how to control it, see
`variables`: Collect the variables that are passed to GraphQL operations.

The operation name and type are always collected. | | `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values.

For instrumented MCP servers, `mcp` takes precedence over these values. | -| `mcp` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of incoming MCP requests: tool call arguments, prompt arguments, and the message payload of logging notifications.

`outputs`: Collect the content of MCP responses, such as tool results and prompt messages.

Metadata, such as the method name, tool or prompt name, session, protocol version, content counts, and error status, is always collected. The `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` take precedence over these values. If you don't set a field, MCP servers use the matching `genAI` field. Requires SDK version `11.9.0` or newer. In earlier versions, only `genAI` controls MCP content. | +| `mcp` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of incoming MCP requests: tool call arguments, prompt arguments, and the message payload of logging notifications.

`outputs`: Collect the content of MCP responses, such as tool results and prompt messages.

Metadata, such as the method name, tool or prompt name, session, protocol version, content counts, and error status, is always collected. The `recordInputs` and `recordOutputs` options of [`wrapMcpServerWithSentry`](/platform-redirect/?next=%2Fmcp-monitoring%2F) take precedence over these values. If you don't set a field, MCP servers use the matching `genAI` field. Requires SDK version `11.9.0` or newer. In earlier versions, only `genAI` controls MCP content. | | `databaseQueryData` | `boolean` | `true` | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data.

The sanitized or parameterized query text (`db.query.text`) is **not** controlled by this option. Structural metadata, such as the database system, query summary, operation name, and table, is also **always** collected. | | `queues` | `boolean` | `true` | Collect the arguments passed to tasks within queues. For Kafka, this is the message key. Structural metadata, such as the messaging system, the destination name, and the operation, is always collected. | | `stackFrameVariables` | `CollectBehavior` | `true` | Capture local variable values in stack frames. Allow/deny lists match variable names. | diff --git a/docs/platforms/javascript/common/data-management/data-collected/index.mdx b/docs/platforms/javascript/common/data-management/data-collected/index.mdx index 94f5e90e247c7e..2e5e9dc32fd02c 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -286,6 +286,8 @@ Sentry.init({ }); ``` + + ## MCP Requests And Responses When you instrument an MCP server, the SDK always sends metadata like the method name, the tool or prompt name, the session, and the error status. @@ -306,9 +308,11 @@ Sentry.init({ }); ``` - To control recording for a single server, use the `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry`. They take precedence over `dataCollection.mcp`. + To control recording for a single server, use the `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry`. They take precedence over `dataCollection.mcp`. The `dataCollection.mcp` option requires SDK version `11.9.0` or newer. In earlier versions, `dataCollection.genAI` controls MCP content. + + diff --git a/docs/product/mcp-servers/getting-started.mdx b/docs/product/mcp-servers/getting-started.mdx index 94bb7927e437f2..56356a65c06e03 100644 --- a/docs/product/mcp-servers/getting-started.mdx +++ b/docs/product/mcp-servers/getting-started.mdx @@ -54,7 +54,7 @@ On Cloudflare Workers, automatic instrumentation requires building with the Sent #### Options -Pass these options to `wrapMcpServerWithSentry` to configure a specific server, including one the SDK already instrumented automatically. The `recordInputs` and `recordOutputs` options require Sentry JavaScript SDK version `10.33.0` or newer. +Pass these options to [`wrapMcpServerWithSentry`](/platform-redirect/?next=%2Fmcp-monitoring%2F) to configure a specific server, including one the SDK already instrumented automatically. The `recordInputs` and `recordOutputs` options require Sentry JavaScript SDK version `10.33.0` or newer. ##### `recordInputs`