RudderStack MCP

What RudderStack MCP does

RudderStack MCP exposes a hosted Model Context Protocol endpoint for working with RudderStack workspace data and control-plane features. AI assistants and developer tools can use it to inspect workspace settings, pipelines, schemas, metrics, profiles, audiences, documentation, and service status.

The server also includes selected write capabilities. Depending on the authorized user's permissions, tools can switch the active workspace, create or update audiences, connect audiences to destinations, create or update transformations, and connect transformations to destinations. This makes the server relevant for both operational investigation and controlled RudderStack configuration work.

How it works

The hosted endpoint is available at https://mcp.rudderstack.com/mcp and uses Streamable HTTP transport. A compatible MCP client connects to that URL, then starts a browser-based RudderStack login and authorization flow on the first connection.

Authentication uses OAuth 2.0 with PKCE and dynamic client registration. After authorization, tool calls run with the permissions of the RudderStack user and workspace selected for the session. Clients store the resulting credentials according to their own security model, so access tokens and client secrets are not placed in MCP configuration files.

Setup and configuration

Native remote-MCP clients can use the hosted endpoint directly. Claude can add it as a custom connector, while VS Code and Cursor use workspace or client MCP configuration files. Windsurf and clients without native Streamable HTTP support can invoke the endpoint through mcp-remote:

npx -y mcp-remote https://mcp.rudderstack.com/mcp

For VS Code, create .vscode/mcp.json and start the RudderStack server from the MCP controls. For Cursor, place the corresponding configuration in .cursor/mcp.json and enable it under MCP Tools. The first connection requires browser access for RudderStack sign-in and authorization.

Tools and capabilities

Available tools cover read operations across RudderStack workspace resources, including:

• Workspace settings and active-workspace selection
• Pipelines, schemas, metrics, profiles, and service status
• Audiences and their destination connections
• RudderStack documentation
• Transformation creation, updates, destination connections, and testing

Transformation tests and audience previews do not persist control-plane configuration. They can still execute code or submit temporary work. Some tools are conditionally available, and write operations should be reviewed before approval because they can change workspace configuration.

Limitations and notes

The repository contains documentation, examples, and registry metadata rather than the hosted server implementation. Its MIT license applies to those repository contents; it does not license the hosted server's private implementation.

Tool access follows the permissions of the authorized RudderStack user and workspace. Review write calls carefully, and avoid sharing access tokens, workspace IDs, event payloads, customer data, or credentials in public issue reports. The hosted service is intended for RudderStack workspaces and requires an MCP client that can use Streamable HTTP directly or through mcp-remote.