RudderStack MCP Beta

RudderStack MCP is in Public Beta as part of RudderStack’s Early Access Program, where we work with early users and customers to test new features and get feedback before making them generally available.

Contact the Product team if you have any questions.

Overview

RudderStack MCP connects your AI assistant to your RudderStack workspace via the Model Context Protocol. Debug delivery errors, monitor pipelines, write and test transformations, review audit logs — all through natural language.

RudderStack MCP works with any MCP-compatible client like Claude, Codex, Cursor, Visual Studio Code (GitHub Copilot), etc.

See the Connect guide to get started.

What you can do

This section lists the capabilities of RudderStack MCP.

Monitor and debug pipelines

• Investigate destination delivery errors and get root cause analysis
• Check warehouse upload status and table-level processing details
• Stream live events to verify data flow in real time
• Review audit logs to track workspace changes

Manage sources and destinations

• View all sources, destinations, and their connections
• Inspect source and destination configurations
• Analyze event metrics — volume, success/failure rates, latency
• Detect duplicate or similar event names across sources

Build and test transformations

• Write transformation code and test it against sample events before deploying
• Browse pre-built transformation templates
• Monitor transformation performance and latency
• Connect transformations to destinations

Enforce data governance

• Review Tracking Plans and their event schemas
• Check Tracking Plan validation metrics and violations
• Explore the Data Catalog events and properties across your workspace

Query documentation

• Ask questions about RudderStack features and get AI-generated answers with source citations

Example prompts

Here are a few prompts to get you started:

“Give me a health check of my data pipelines over the past week — show error rates, volume trends, and any issues.”

“My Facebook Conversions API destination has failing events. What’s causing the errors?”

“Find event names on my JavaScript source that look like duplicates or typos.”

“How do I set up a BigQuery destination with a service account key?”

Security and privacy

• PII protection: Event properties, traits, and request bodies are masked before being sent to your AI assistant. Structural metadata like event names and types remain visible, but personally identifiable information in payload values is never exposed
• Access control: The MCP server accesses only the workspaces and resources your RudderStack account has permission to access
• Limited write operations: The only write operations are creating or updating transformations, and connecting them to destinations. No sources or destinations are created or deleted
• OAuth authentication: Secure browser-based login with automatic token refresh. No credentials are stored in your client configuration

Limitations

• RudderStack MCP is in Public Beta — the features and available tools may change.
• Write operations are limited to transformations only
• AI-generated documentation answers can occasionally be inaccurate — verify with official documentation

Feedback

Contact RudderStack Support to provide feedback on RudderStack MCP and share your suggestions for improvement.