---
title: "Set Up"
description: "Learn how to set up Sentry MCP Monitoring"
url: https://docs.sentry.io/product/mcp-servers/getting-started/
---

# Set Up

Sentry MCP Monitoring helps you track and debug Model Context Protocol (MCP) implementations using our supported SDKs and integrations. Monitor your complete MCP workflows from client connections to server responses, including tool executions, resource access, and protocol communications.

To start sending MCP data to Sentry, make sure you've created a Sentry project for your MCP-enabled repository and follow the guide below:

## [Supported SDKs](https://docs.sentry.io/product/mcp-servers/getting-started.md#supported-sdks)

### [JavaScript - MCP Server](https://docs.sentry.io/product/mcp-servers/getting-started.md#javascript---mcp-server)

##### Version requirement

MCP Monitoring requires Node SDK version `9.46.0` or newer.

The example below uses [`@modelcontextprotocol/sdk`](https://www.npmjs.com/package/@modelcontextprotocol/sdk) 1.x. The Sentry wrapper automatically captures spans for MCP server workflows, including tool executions, resource access, and client connections.

#### [Quick Start with MCP Server](https://docs.sentry.io/product/mcp-servers/getting-started.md#quick-start-with-mcp-server)

```javascript
import * as Sentry from "@sentry/node";
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";

// Sentry init needs to be above everything else
Sentry.init({
  dsn: "https://<key>@o<orgId>.ingest.sentry.io/<projectId>",
  tracesSampleRate: 1.0,
});

// Wrap every MCP server instance
const server = Sentry.wrapMcpServerWithSentry(
  new McpServer({
    name: "my-mcp-server",
    version: "1.0.0",
  }),
);

...
```

Stable `@modelcontextprotocol/server` 2.x support requires Sentry JavaScript SDK version `10.70.0` or newer. For framework-specific setup, see MCP Monitoring for [Node.js](https://docs.sentry.io/platforms/javascript/guides/node/mcp-monitoring.md), [Hono](https://docs.sentry.io/platforms/javascript/guides/hono/mcp-monitoring.md), or [Cloudflare](https://docs.sentry.io/platforms/javascript/guides/cloudflare/mcp-monitoring.md).

#### [Options](https://docs.sentry.io/product/mcp-servers/getting-started.md#options)

The `recordInputs` and `recordOutputs` options require Sentry JavaScript SDK version `10.33.0` or newer.

##### [`recordInputs`](https://docs.sentry.io/product/mcp-servers/getting-started.md#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`.

##### [`recordOutputs`](https://docs.sentry.io/product/mcp-servers/getting-started.md#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`.

#### [Cloudflare Workers](https://docs.sentry.io/product/mcp-servers/getting-started.md#cloudflare-workers)

MCP work on Cloudflare can finish after the Worker returns an HTTP response. Configure `traceLifecycle: "stream"` so spans are sent when they finish instead of depending on a static request snapshot. This requires `@sentry/cloudflare` version `10.49.0` or newer.

See [MCP Monitoring on Cloudflare](https://docs.sentry.io/platforms/javascript/guides/cloudflare/mcp-monitoring.md) for the configuration and filtering differences in stream mode.

### [Python - MCP Server](https://docs.sentry.io/product/mcp-servers/getting-started.md#python---mcp-server)

##### Version requirement

MCP Monitoring requires Python SDK version `2.43.0` or newer.

The Sentry Python SDK supports MCP Monitoring for the [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk) (both low-level and FastMCP APIs) and [standalone FastMCP](https://gofastmcp.com/getting-started/welcome). The integration automatically captures spans for your MCP server workflows, including tool executions, resource access, and prompt handling.

#### [Quick Start](https://docs.sentry.io/product/mcp-servers/getting-started.md#quick-start)

```python
import sentry_sdk
from sentry_sdk.integrations.mcp import MCPIntegration
from mcp.server.fastmcp import FastMCP

# Sentry init needs to be above everything else
sentry_sdk.init(
    dsn="https://<key>@o<orgId>.ingest.sentry.io/<projectId>",
    traces_sample_rate=1.0,
    # Optional: Enable to capture tool call arguments and results in Sentry, which may include PII
    send_default_pii=True,
    integrations=[MCPIntegration()],
)

# Create the MCP server
mcp = FastMCP("Example MCP Server")

# Define a tool
@mcp.tool()
async def calculate_sum(a: int, b: int) -> int:
    """Add two numbers together."""
    return a + b

# Run the server
mcp.run()
```

*Other available variations of the above snippet: FastMCP, MCP Low-Level API*