RudderStack MCP connects Claude to your RudderStack workspace so you can debug customer data pipelines by asking instead of clicking through dashboards.
Debug delivery: get destination errors with sample events and the destination's API response, success and failure rates, latency, and a live tail of events across sources, transformations and destinations.
Check warehouse and Reverse ETL syncs: upload history, failed loads, table-level detail and sync runs.
Enforce your tracking plan: violation counts and samples per event, tracking plan versions, the Data Catalog, and duplicate or misspelled event names.
Build transformations: start from a template, write JavaScript or Python, test it on sample events, then save it and connect it to a destination.
Build audiences: explore your data graph, preview an audience's size, create it, and sync it to an activation destination.
Investigate changes with audit logs, configuration details, Profiles runs and RudderStack status incidents, and ask RudderStack's docs anything.
Claude acts with your RudderStack permissions, only in workspaces you can already access. Only a few tools write, and only to transformations and audiences; nothing can be deleted, and sources and destinations can't be created or changed. Event properties, traits and request bodies are hashed before they reach Claude.
