Skip to main content
Glama
Sign In
RudderStack MCP

RudderStack MCP

Official
by rudderlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

RudderStack MCP

AllMCPs Verified

Connect AI assistants and developer tools to your RudderStack workspace through the hosted Model Context Protocol (MCP) server.

IMPORTANT

This public repository contains registry metadata, setup examples, and documentation for the hosted RudderStack MCP server. It doesnot contain the server implementation source code, and its MIT license applies only to this repository's contents.

Connect

Native remote-MCP clients can connect directly to:

https://mcp.rudderstack.com/mcp

On the first connection, the client opens a browser so you can sign in to RudderStack and authorize access. No token or client secret belongs in these configuration files.

Claude

In Settings → Connectors, choose Add custom connector, name it RudderStack, and enter https://mcp.rudderstack.com/mcp.

For clients that require a local stdio command, use:

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

See examples/.mcp.json for the corresponding JSON configuration.

VS Code

Create .vscode/mcp.json in your workspace using examples/.vscode/mcp.json, then start the rudderstack server from VS Code's MCP controls.

Cursor

Copy examples/.cursor/mcp.json to .cursor/mcp.json, then enable rudderstack in Settings → Tools & Integrations → MCP Tools.

Cline

In Cline, open MCP Servers → Remote Servers, add a server named rudderstack with URL https://mcp.rudderstack.com/mcp and transport Streamable HTTP, then sign in to RudderStack in the browser when prompted.

Gemini CLI

Install the extension from this repository:

gemini extensions install https://github.com/rudderlabs/rudderstack-mcp

Then run /mcp auth rudderstack in Gemini CLI, sign in to RudderStack in the browser, and approve access. The extension manifest is gemini-extension.json.

Windsurf and other clients

Add a custom MCP server with command npx and arguments -y, mcp-remote, and https://mcp.rudderstack.com/mcp. Clients with native Streamable HTTP support can use the endpoint directly.

Related MCP server: CloudCrane MCP

Authentication and permissions

RudderStack uses OAuth 2.0 with PKCE and accepts client ID metadata documents alongside dynamic client registration. A compatible client discovers the authorization metadata, opens RudderStack login in your browser, and stores the resulting credentials according to that client's security model.

Tools run with the permissions of the RudderStack user and workspace you authorize. Review tool calls before approving them, especially write operations. Workspace tools require workspace_id (or workspaceId) from user_details on every call; the endpoint is stateless.

Tool access

Most tools inspect workspace settings, pipelines, schemas, metrics, profiles, audiences, documentation, and service status. Some tools make control-plane changes or trigger syncs, including:

  • creating or updating audiences;

  • connecting audiences to destinations;

  • creating rETL audience activations;

  • triggering audience-activation syncs;

  • creating or updating transformations; and

  • connecting transformations to destinations.

Transformation tests, audience previews, Reverse ETL failed-record reads, and audience-activation planning do not persist control-plane configuration, but they can execute code or submit temporary warehouse work. See docs/tools.md for every tool exposed by the hosted /mcp endpoint, its classification, and conditionally available tools.

Security and support

  • Report suspected vulnerabilities privately as described in SECURITY.md.

  • For product bugs, use the bug report form.

  • For tool requests, use the tool request form.

  • Never post access tokens, workspace IDs, event payloads, customer data, or credentials in a public issue.

Resources

License

The documentation, examples, and metadata in this repository are available under the MIT License. This license does not apply to the hosted server's private implementation.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-console

    sanjarbiy
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables connecting a CLI agent to a team's shared workspace, providing secure authentication and access to workspace tools.
    -

  • CloudCrane MCP

    cloudcrane-dev
    A
    license
    Not graded
    quality
    B
    maintenance
    Connects an AI agent over Streamable HTTP to a workspace so it can read datasets, contracts, runs and receipts, and, when the owner permits, create fields and value sets, start runs and publish releases — while each deployed tool is also served as its own endpoint whose schema is generated from the owner's contracts. Every value comes with a receipt and safety exclusions are enforced in the query, with sensitive actions like approving review items or publishing past the accuracy gate reserved for a person.
    MIT
  • Skysay MCP

    Skysay MCPofficial

    skysay-ai
    A
    license
    Not graded
    quality
    B
    maintenance
    Connects AI assistants to an existing Skysay workspace so they can inspect and manage voice agents, phone numbers, calls, SMS messages, and campaigns, with a read-only endpoint available for fixed read-only access.
    MIT

  • Octopus Deploy Official MCP

    suzuki79381
    A
    license
    Not graded
    quality
    A
    maintenance
    Connects AI assistants to an Octopus instance so they can inspect, query, and diagnose deployment state, and, when write tools are enabled, create releases, deploy them, and run runbooks. Supports read-only mode and toolset scoping for safer, more controlled access.
    453 npm
    MIT