← ClaudeAtlas

rudder-mcp-workflowlisted

Connects AI agents to RudderStack via MCP tool calls for catalog, sources, destinations, transformations, and live events. Use when connecting an AI agent to RudderStack's MCP server, driving RudderStack via MCP, or mentions of mcp.rudderstack.com.
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack MCP Workflow RudderStack's hosted MCP server at `mcp.rudderstack.com` exposes a RudderStack workspace as an MCP endpoint so AI agents (Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, or any MCP client) can inspect and drive workspace resources via tool calls. Authoritative docs: https://mcp.rudderstack.com/docs. ## When to use The user wants an AI agent to drive RudderStack, mentions RudderStack + MCP, asks about `mcp.rudderstack.com`, or wants to configure MCP tool access for a RudderStack workspace. ## Preflight Before running any workflow, verify: - [ ] Your MCP client is configured to connect to `https://mcp.rudderstack.com/mcp` (OAuth, the default) or `https://mcp.rudderstack.com/bearer-auth-mcp` (access token). See `rudder-mcp-setup` for the Claude Code walkthrough of both; the official docs cover Claude Desktop, Cursor, VS Code, Windsurf, and the claude.ai web UI. - [ ] OAuth route: browser sign-in to your RudderStack account completed on first tool use. Access-token route: `RUDDERSTACK_ACCESS_TOKEN` was exported in the shell that started the client, and the `X-Workspace-ID` header holds the workspace ID. - [ ] `mcp.rudderstack.com` is reachable on port 443 from your network. ## Client configuration If `claude mcp list` already shows a server at `https://mcp.rudderstack.com/mcp` or `https://mcp.rudderstack.com/bearer-auth-mcp`, under `plugin:rudder-core:rudderstack` (the rudder-core plugin's entry) or any other name, use it and add nothing