RudderStack integration for AI agents.
RudderStack integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves RudderStack tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real RudderStack actions, managed and audited.
Your user connects RudderStack once; your agent can then rudderStack brings agentic power to the entire customer data lifecycle — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants RudderStack access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported RudderStack tools.
0 tools are generated from the published RudderStack catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.
No tools match “”.
RudderStack integration, answered
- How do AI agents use RudderStack through Open Connector?
- Your user connects RudderStack once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes RudderStack tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a RudderStack MCP server?
- Yes. Open Connector can serve RudderStack as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call RudderStack actions with credentials injected server-side.
- Where do RudderStack credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents RudderStack — keep the keys.
Open source, self-hostable, with RudderStack credentials that never leave your infrastructure. Run it from source today.