Skip to content
actionlake
Start free

Connectors · Observability & analytics

RudderStack MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to RudderStack and the rest of your systems. It gives your agent 66 RudderStack actions (29 reads, 25 writes and 12 that wait for a confirmation) and holds the RudderStack credential itself, so the agent never does. It paces RudderStack's limits and records every call.

Connect RudderStack freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "rudderstack.catalog_events.list",  intent: "check which RudderStack account is connected"}# List data catalog events · read · 1 upstream call
  • 66actionsin one signed file
  • 29readlook, never change
  • 25writecreate and update
  • 12wait for a yesdestructive, confirmed first

Set up

Connect RudderStack in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect RudderStack.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • access_tokenRudderStack Service Access Token (Settings > Access Management): workspace-level for most actions,…
    • regionYour RudderStack region
    account { op: "connections.requirements", service: "rudderstack" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "rudderstack.catalog_events.list" }# list data catalog events · read · 1 upstream callcheck { action: "rudderstack.catalog_events.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

RudderStack at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
access_token
Setup fields
region
Limits we pace to
600 calls a minute, per connection
API covered
RudderStack (data catalog, tracking plans, transformations, reverse ETL, profiles, suppression) API RudderStack control-plane APIs (v2, transformations, v0 test) as documented 2026-10, at your region's rudderstack.com address, set when you connect
Built from
RudderStack's documentation, read 23 October 2026rudderstack.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
29 of 29 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line RudderStack up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in RudderStack.

66 actions in 19 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 29readlook, never change
  • 25writecreate and update
  • 12destructivewait for a confirmation

  1. Transformations

    7

    2 read · 3 write · 2 destructive

    List transformations · Get transformation · Connect transformation to destination · Create transformation

  2. Libraries

    6

    2 read · 3 write · 1 destructive

    List transformation libraries · Get transformation library · Create transformation library · Publish transformation and library revisions

  3. Tracking plan events

    6

    2 read · 3 write · 1 destructive

    List tracking plan events · Get tracking plan event · Remove event from tracking plan · Upsert tracking plan event by IDs

  4. Catalog custom types

    5

    2 read · 2 write · 1 destructive

    List custom data types · Get custom data type · Create custom data type · Update custom data type

  5. Catalog events

    5

    2 read · 2 write · 1 destructive

    List data catalog events · Get data catalog event · Create data catalog event · Delete data catalog event

  6. Catalog properties

    5

    2 read · 2 write · 1 destructive

    List data catalog properties · Get data catalog property · Create data catalog property · Update data catalog property

  7. Tracking plans

    5

    2 read · 2 write · 1 destructive

    List tracking plans · Get tracking plan · Create tracking plan · Update tracking plan

  8. Catalog categories

    4

    2 read · 1 write · 1 destructive

    List event categories · Get event category · Create event category · Delete event category

11 more areas · 23 actions
  • Retl syncs 4
  • Tracking plan sources 4
  • Regulations 3
  • Library versions 2
  • Profiles runs 2
  • Test 2
  • Transformation versions 2
  • Audit logs 1
  • Destinations 1
  • Organization usage 1
  • Sources 1

Top actions

The RudderStack API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of RudderStack's 5 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
rudderstack.catalog_events.listList data catalog eventsList data catalog events.readanalytics.tracked_event.list10 connectors
rudderstack.audit_logs.listList audit logsList audit logs.readplatform.activity_entry.list43 connectors
rudderstack.catalog_events.getGet data catalog eventGet data catalog event.readanalytics.tracked_event.get5 connectors
rudderstack.catalog_events.createCreate data catalog eventCreate data catalog event.writeanalytics.tracked_event.create12 connectors
rudderstack.catalog_events.deleteDelete data catalog eventDelete data catalog event.destructiveanalytics.tracked_event.delete2 connectors
rudderstack.sources.listList sourcesList sources.readthis connector
rudderstack.libraries.listList transformation librariesList transformation libraries.readthis connector
rudderstack.retl_syncs.listList reverse ETL syncsList reverse ETL syncs.readthis connector
rudderstack.regulations.listList user suppression regulationsList user suppression regulations.readthis connector
rudderstack.destinations.listList destinationsList destinations.readthis connector
rudderstack.test.sourceTest event against sourceTest event against source.writethis connector
rudderstack.libraries.createCreate transformation libraryCreate transformation library.writethis connector

Try it

Prompts to paste into Claude.

Each one names the RudderStack actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List data catalog events in RudderStack and tell me what stands out.

    callsrudderstack.catalog_events.list

  2. Writewrite

    Create data catalog event in RudderStack. Show me exactly what you will send before you save it.

    callsrudderstack.catalog_events.create

Governance for RudderStack

Destructive actions wait for a yes.

12 RudderStack actions are destructive. These are all of them:

  • Delete data catalog eventrudderstack.catalog_events.delete
  • Delete transformation libraryrudderstack.libraries.delete
  • Delete tracking planrudderstack.tracking_plans.delete
  • Delete transformationrudderstack.transformations.delete
  • Delete event categoryrudderstack.catalog_categories.delete
  • Delete data catalog propertyrudderstack.catalog_properties.delete
  • Delete custom data typerudderstack.catalog_custom_types.delete
  • Remove event from tracking planrudderstack.tracking_plan_events.delete
  • Disconnect source from tracking planrudderstack.tracking_plan_sources.disconnect
  • Disconnect transformation from destinationrudderstack.transformations.disconnect_destination
  • Cancel reverse ETL syncrudderstack.retl_syncs.stop
  • Cancel user suppression regulationrudderstack.regulations.cancel

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dorudderstack.catalog_events.deleteconfirm_policy: human

Delete data catalog event?

intent: the user asked me to delete data catalog event

run suspended · waiting for a named person · key rudderstack-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "rudderstack-agent",  allowed_actions: ["rudderstack.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "rudderstack.catalog_events.delete", approver: "[email protected]" },    { match: "rudderstack.libraries.delete", approver: "[email protected]" },    { match: "rudderstack.tracking_plans.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to RudderStack only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What RudderStack costs on actionlake.

Every RudderStack action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call RudderStack refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 66 RudderStack actions
  • 7actions pageeach page of a long list is one call
  • 29reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every RudderStack action.

66 actions by area: the id your agent calls, what it does, and its effect.

Transformations7
  • rudderstack.transformations.connect_destinationConnect transformation to destinationwrite
  • rudderstack.transformations.createCreate transformationwrite
  • rudderstack.transformations.deleteDelete transformationdestructive
  • rudderstack.transformations.disconnect_destinationDisconnect transformation from destinationdestructive
  • rudderstack.transformations.getGet transformationread
  • rudderstack.transformations.listList transformationsread
  • rudderstack.transformations.updateUpdate transformationwrite
Libraries6
  • rudderstack.libraries.createCreate transformation librarywrite
  • rudderstack.libraries.deleteDelete transformation librarydestructive
  • rudderstack.libraries.getGet transformation libraryread
  • rudderstack.libraries.listList transformation librariesread
  • rudderstack.libraries.publish_revisionsPublish transformation and library revisionswrite
  • rudderstack.libraries.updateUpdate transformation librarywrite
Tracking plan events6
  • rudderstack.tracking_plan_events.deleteRemove event from tracking plandestructive
  • rudderstack.tracking_plan_events.getGet tracking plan eventread
  • rudderstack.tracking_plan_events.listList tracking plan eventsread
  • rudderstack.tracking_plan_events.upsert_by_idsUpsert tracking plan event by IDswrite
  • rudderstack.tracking_plan_events.upsert_with_propertiesUpsert tracking plan event with propertieswrite
  • rudderstack.tracking_plan_events.upsert_with_rulesUpsert tracking plan event with ruleswrite
Catalog custom types5
  • rudderstack.catalog_custom_types.createCreate custom data typewrite
  • rudderstack.catalog_custom_types.deleteDelete custom data typedestructive
  • rudderstack.catalog_custom_types.getGet custom data typeread
  • rudderstack.catalog_custom_types.listList custom data typesread
  • rudderstack.catalog_custom_types.updateUpdate custom data typewrite
Catalog events5
  • rudderstack.catalog_events.createCreate data catalog eventwrite
  • rudderstack.catalog_events.deleteDelete data catalog eventdestructive
  • rudderstack.catalog_events.getGet data catalog eventread
  • rudderstack.catalog_events.listList data catalog eventsread
  • rudderstack.catalog_events.updateUpdate data catalog eventwrite
Catalog properties5
  • rudderstack.catalog_properties.createCreate data catalog propertywrite
  • rudderstack.catalog_properties.deleteDelete data catalog propertydestructive
  • rudderstack.catalog_properties.getGet data catalog propertyread
  • rudderstack.catalog_properties.listList data catalog propertiesread
  • rudderstack.catalog_properties.updateUpdate data catalog propertywrite
Tracking plans5
  • rudderstack.tracking_plans.createCreate tracking planwrite
  • rudderstack.tracking_plans.deleteDelete tracking plandestructive
  • rudderstack.tracking_plans.getGet tracking planread
  • rudderstack.tracking_plans.listList tracking plansread
  • rudderstack.tracking_plans.updateUpdate tracking planwrite
Catalog categories4
  • rudderstack.catalog_categories.createCreate event categorywrite
  • rudderstack.catalog_categories.deleteDelete event categorydestructive
  • rudderstack.catalog_categories.getGet event categoryread
  • rudderstack.catalog_categories.listList event categoriesread
Retl syncs4
  • rudderstack.retl_syncs.getGet reverse ETL syncread
  • rudderstack.retl_syncs.listList reverse ETL syncsread
  • rudderstack.retl_syncs.startStart reverse ETL syncwrite
  • rudderstack.retl_syncs.stopCancel reverse ETL syncdestructive
Tracking plan sources4
  • rudderstack.tracking_plan_sources.connectConnect source to tracking planwrite
  • rudderstack.tracking_plan_sources.disconnectDisconnect source from tracking plandestructive
  • rudderstack.tracking_plan_sources.listList tracking plan sourcesread
  • rudderstack.tracking_plan_sources.updateUpdate tracking plan source configurationwrite
Regulations3
  • rudderstack.regulations.cancelCancel user suppression regulationdestructive
  • rudderstack.regulations.createCreate user suppression regulationwrite
  • rudderstack.regulations.listList user suppression regulationsread
Library versions2
  • rudderstack.library_versions.getGet library versionread
  • rudderstack.library_versions.listList library versionsread
Profiles runs2
  • rudderstack.profiles_runs.get_statusGet Profiles run statusread
  • rudderstack.profiles_runs.startRun Profiles projectwrite
Test2
  • rudderstack.test.destinationTest event against destinationwrite
  • rudderstack.test.sourceTest event against sourcewrite
Transformation versions2
  • rudderstack.transformation_versions.getGet transformation versionread
  • rudderstack.transformation_versions.listList transformation versionsread
Audit logs1
  • rudderstack.audit_logs.listList audit logsread
Destinations1
  • rudderstack.destinations.listList destinationsread
Organization usage1
  • rudderstack.organization_usage.get_event_metricsGet organization event usageread
Sources1
  • rudderstack.sources.listList sourcesread

Questions

The RudderStack MCP server, answered.

Is there a RudderStack MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 66 RudderStack actions across transformations, libraries, tracking plan events and catalog custom types, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by RudderStack.

What do I need to connect RudderStack?

RudderStack Service Access Token (Settings > Access Management): workspace-level for most actions,…. Plus your region. The free call account { op: "connections.requirements", service: "rudderstack" } lists exactly what to paste.

Can an AI agent delete or change things in RudderStack?

Only if its key allows it, and only with an explicit confirmation. 12 RudderStack actions are destructive, including delete data catalog event, delete transformation library and delete tracking plan. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my RudderStack API limit?

actionlake paces every call to the limits in the RudderStack service file: 600 calls a minute per connection. Repeated reads are answered from cache (29 RudderStack actions can be), which never reaches RudderStack.

What does a RudderStack action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (7 RudderStack actions page). Cache hits, searches, dry runs and calls RudderStack refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which RudderStack API does it cover?

The RudderStack (data catalog, tracking plans, transformations, reverse ETL, profiles, suppression) API RudderStack control-plane APIs (v2, transformations, v0 test) as documented 2026-10 at your region's rudderstack.com address, set when you connect. It is built from RudderStack's documentation as read on 23 October 2026. 66 actions in 19 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my RudderStack data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your RudderStack credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like RudderStack

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by RudderStack; the name is the vendor's own. Counts are from the RudderStack service file, version 1.0.0.

Give your agent RudderStack today.

Connect RudderStack freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.