docs(js): Link wrapMcpServerWithSentry and document mcp defaults for MCP servers (#20106)

Author: sentry-junior[bot]

docs/platforms/javascript/common/configuration/options.mdx

@@ -139,8 +139,8 @@ For more on what data Sentry collects and how to control it, see <PlatformLink t
 | `httpBodies`          | `HttpBodyCollectionTarget[]` | all types     | Body types to collect: `"incomingRequest"`, `"outgoingRequest"`, `"incomingResponse"`, `"outgoingResponse"`. Set to `[]` to disable. |
 | `urlQueryParams`      | `CollectBehavior`            | `true`        | Collect URL query parameters. Parameter names are always included. The SDK replaces the values of sensitive parameters with `[Filtered]`. |
 | `graphQL`             | `{ document?, variables? }`  | both `true`   | `document`: Collect the GraphQL document (the query or mutation source text). <br /><br /> `variables`: Collect the variables that are passed to GraphQL operations. <br /><br /> 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. <br /><br /> `outputs`: Collect the content of generative AI outputs, such as completion text and tool call results. <br /><br /> Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values. |
-| `mcp`                 | `{ inputs?, outputs? }`      | both `true`   | Available in SDK version `11.9.0` and above. <br /><br /> `inputs`: Collect the content of incoming MCP requests, such as tool call arguments, prompt arguments, and the payload of MCP logging notifications. <br /><br /> `outputs`: Collect the content of MCP responses, such as tool results and prompt result messages. <br /><br /> Metadata, such as the method name, the tool or prompt name, and error status, is always collected. A field you don't set falls back to the matching `genAI` field. The `recordInputs` and `recordOutputs` options of `wrapMcpServerWithSentry` 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. <br /><br /> `outputs`: Collect the content of generative AI outputs, such as completion text and tool call results. <br /><br /> Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values. <br /><br /> For instrumented MCP servers, `mcp` takes precedence over these values. |
+| `mcp`                 | `{ inputs?, outputs? }`      | both `true`   | Available in SDK version `11.9.0` and above. <br /><br /> `inputs`: Collect the content of incoming MCP requests, such as tool call arguments, prompt arguments, and the payload of MCP logging notifications. <br /><br /> `outputs`: Collect the content of MCP responses, such as tool results and prompt result messages. <br /><br /> Metadata, such as the method name, the tool or prompt name, and error status, is always collected. A field you don't set falls back to the matching `genAI` field. The `recordInputs` and `recordOutputs` options of [`wrapMcpServerWithSentry`](/platform-redirect/?next=%2Fmcp-monitoring%2F) take precedence over these values. |
 | `databaseQueryData`   | `boolean`                    | `true`        | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data. <br /><br /> 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. |

docs/platforms/javascript/common/data-management/data-collected/index.mdx

@@ -309,7 +309,7 @@ Sentry.init({
 
   If you don't set a field of `dataCollection.mcp`, the SDK uses the matching `dataCollection.genAI` field instead. In SDK versions before `11.9.0`, `dataCollection.genAI` is the only global setting for MCP content.
 
-  To control recording for a specific server, use the `recordInputs` and `recordOutputs` options of <PlatformLink to="/mcp-monitoring/">`wrapMcpServerWithSentry`</PlatformLink>. They take precedence over the `dataCollection` settings.
+  To control recording for a specific server, use the `recordInputs` and `recordOutputs` options of <PlatformLink to="/mcp-monitoring/#configure-input-and-output-recording">`wrapMcpServerWithSentry`</PlatformLink>. They take precedence over the `dataCollection` settings.
   </PlatformCategorySection>
 </PlatformSection>
 

docs/product/mcp-servers/getting-started.mdx

@@ -54,23 +54,23 @@ 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`
 
 _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`, 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`
 
 _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`, 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