RudderStack Transformation for AI agents
RudderStack Transformation manages code transformations and libraries that reshape event data as it flows through customer data pipelines. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in RudderStack Transformation.
Review a transformation's code
Get a transformation's current version before changing how it reshapes incoming event data.
Update pipeline logic
Update a transformation once a new field needs to be added to outgoing events.
Confirm before deleting a library
List all libraries first, then delete one only after confirming no transformation still depends on it.
12 RudderStack Transformation actions, graded by risk.
Every RudderStack Transformation action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
8Look things up. Allowed by default.
- rudderstack_transformation.get_libraryGet library by ID
- rudderstack_transformation.list_librariesList All Libraries
- rudderstack_transformation.get_transformationGet Transformation
- rudderstack_transformation.get_library_versionGet Library Version
- rudderstack_transformation.list_transformationsList All Transformations
- rudderstack_transformation.list_library_versionsList Library Versions
- rudderstack_transformation.get_transformation_versionGet Transformation Version
- rudderstack_transformation.list_transformation_versionsList Transformation Versions
write
3Create and change things. Allow, or ask the user first.
- rudderstack_transformation.create_libraryCreate Library
- rudderstack_transformation.create_transformationCreate Transformation
- rudderstack_transformation.update_transformationUpdate Transformation
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- rudderstack_transformation.delete_transformationDelete Transformation
RudderStack Transformation in three steps.
- 01Your users connect RudderStack TransformationThey add their RudderStack Transformation username and password on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Library” can wait for the user, and “delete Transformation” can be denied outright.
- 03Any agent can actYour agent calls RudderStack Transformation through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('rudderstack_transformation', { read: 'allow', write: 'ask', // create_library destructive: 'deny', // delete_transformation }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How RudderStack Transformation connects.
Users add their RudderStack Transformation username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same RudderStack Transformation connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use RudderStack Transformation from any agent.
RudderStack Transformation and Arc0, answered.
Can I use RudderStack Transformation with Claude, ChatGPT or Cursor?
Yes. Connect RudderStack Transformation to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the RudderStack Transformation actions you allow.
How do users connect RudderStack Transformation?
Users add their RudderStack Transformation username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which RudderStack Transformation actions can my agent take?
12 in total: 8 read, 3 write and 1 destructive, such as “create Library”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in RudderStack Transformation?
Yes. Actions like “delete Transformation” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call RudderStack Transformation too?
Yes. The same RudderStack Transformation connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug RudderStack Transformation into your agent.
Your users connect RudderStack Transformation once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan