RudderStack Transformations MCP server
17 operations0 webhooks
Create, version, publish and connect RudderStack transformations, and manage the reusable libraries they import.
Use RudderStack Transformations in Claude, ChatGPT, Cursor or another MCP client
Connect RudderStack Transformations once in Corsair, then add one MCP address to your agent.
Building your own app on the Corsair SDK? Get API keys
Try RudderStack Transformations with your agent
Connect RudderStack Transformations, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in RudderStack Transformations on my account, then run one read-only example and show me the result.
RudderStack Transformations tools and triggers
Tools are what your agent can do in RudderStack Transformations through Corsair's MCP server. Triggers are the RudderStack Transformations events a routine can start from.
Transformations
- ConnectWrite
Connect a published transformation to a destination, replacing any transformation already connected to it
transformations.connect
- CreateWrite
Create a transformation; unpublished unless publish is true, and only a published one can be connected to a destination
transformations.create
- DeleteDestructive
Delete a published transformation; its revisions are never deleted
transformations.delete
- DisconnectWrite
Disconnect a transformation from a destination
transformations.disconnect
- GetRead-only
Read one published transformation by ID
transformations.get
- Get VersionRead-only
Read one revision of a transformation
transformations.getVersion
- ListRead-only
List the published transformations in the workspace with their code, language and connected destinations
transformations.list
- List VersionsRead-only
List the revisions of a transformation, newest or oldest first
transformations.listVersions
- UpdateWrite
Update a transformation, which always writes a new revision and makes it live only when publish is true
transformations.update
Libraries
- CreateWrite
Create a reusable library whose importName transformations import it by
libraries.create
- DeleteDestructive
Delete a library by ID
libraries.delete
- GetRead-only
Read one published library by ID
libraries.get
- Get VersionRead-only
Read one revision of a library
libraries.getVersion
- ListRead-only
List the published libraries in the workspace
libraries.list
- List VersionsRead-only
List the revisions of a library, newest or oldest first
libraries.listVersions
- PublishWrite
Publish chosen transformation and library revisions after RudderStack runs their code, so a failing test publishes nothing
libraries.publish
- UpdateWrite
Update a library, writing a new revision and publishing it only when publish is true; the name and language cannot change
libraries.update
Connect RudderStack Transformations to Claude, ChatGPT or Cursor
- 1
Connect RudderStack Transformations in Corsair
Add your RudderStack Transformations API key once in Corsair. Corsair stores the credential encrypted and makes the RudderStack Transformations API calls for your agent, so it never goes into a prompt or a config file. Connect RudderStack Transformations
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs RudderStack Transformations. On a ChatGPT personal plan, connect RudderStack Transformations here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, RudderStack Transformations's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/rudderstacktransform, add the RudderStack Transformations plugin, and connect with an API key. Then call methods like corsair.rudderstacktransform.api.libraries.create() from your app. Corsair keeps each tenant isolated.
Yes. RudderStack Transformations requires an API key from your RudderStack Transformations account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit RudderStack Transformations, GitHub, Notion, Stripe, and the rest. Trigger RudderStack Transformations from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for create, version, publish and connect RudderStack transformations, and manage the reusable libraries they import. Common builds include sync jobs, admin tooling, and agents that call RudderStack Transformations APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per RudderStack Transformations API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/rudderstacktransform in the open repo. When RudderStack Transformations ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your RudderStack Transformations data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store RudderStack Transformations data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put RudderStack Transformations on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive RudderStack Transformations operations. You can change a link's mode at hub.corsair.dev/me.