# How to integrate RudderStack Transformation MCP with CrewAI

```json
{
  "title": "How to integrate RudderStack Transformation MCP with CrewAI",
  "toolkit": "RudderStack Transformation",
  "toolkit_slug": "rudderstack_transformation",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/rudderstack_transformation/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/rudderstack_transformation/framework/crew-ai.md",
  "updated_at": "2026-03-29T06:48:30.658Z"
}
```

## Introduction

This guide walks you through connecting RudderStack Transformation to CrewAI using the Composio tool router. By the end, you'll have a working RudderStack Transformation agent that can list all transformations for workspace marketing-pipeline, update the transformation script for user-events, delete transformation named old-data-cleanup through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a RudderStack Transformation account through Composio's RudderStack Transformation MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate RudderStack Transformation with

- [OpenAI Agents SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/rudderstack_transformation/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/rudderstack_transformation/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/rudderstack_transformation/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/rudderstack_transformation/framework/cli)
- [Google ADK](https://composio.dev/toolkits/rudderstack_transformation/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/rudderstack_transformation/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/rudderstack_transformation/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/rudderstack_transformation/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your RudderStack Transformation connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for RudderStack Transformation
- Build a conversational loop where your agent can execute RudderStack Transformation operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

## What is the RudderStack Transformation MCP server, and what's possible with it?

The RudderStack Transformation MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your RudderStack Transformation account. It provides structured and secure access so your agent can perform RudderStack Transformation operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `RUDDERSTACK_TRANSFORMATION_CREATE_LIBRARY` | Create Library | Tool to create a library in RudderStack Transformation. Use when you need to create reusable JavaScript or Python code that can be imported in transformations. Libraries enable code reusability and version maintenance. |
| `RUDDERSTACK_TRANSFORMATION_CREATE_TRANSFORMATION` | Create Transformation | Tool to create a RudderStack transformation. When publish=false (default), creates an unpublished transformation not available to event traffic. When publish=true, publishes the transformation making it live for incoming events and connectable to destinations. |
| `RUDDERSTACK_TRANSFORMATION_DELETE_TRANSFORMATION` | Delete Transformation | Delete a published transformation by ID. Note that RudderStack never deletes a transformation revision. Use this when you need to remove a transformation from the system. |
| `RUDDERSTACK_TRANSFORMATION_GET_LIBRARY` | Get library by ID | Retrieves a single published library by its unique identifier. Use when you need to fetch details of a specific library. |
| `RUDDERSTACK_TRANSFORMATION_GET_LIBRARY_VERSION` | Get Library Version | Tool to retrieve a single library version by library ID and version ID. Use when you need to fetch details of a specific library revision in RudderStack transformations. |
| `RUDDERSTACK_TRANSFORMATION_GET_TRANSFORMATION` | Get Transformation | Tool to retrieve a published transformation by its ID from RudderStack. Use when you need to fetch details about a specific transformation including its code, version, and associated destinations. |
| `RUDDERSTACK_TRANSFORMATION_GET_TRANSFORMATION_VERSION` | Get Transformation Version | Retrieve a single transformation revision by transformation ID and version ID. Use when you need to get details about a specific version of a RudderStack transformation. |
| `RUDDERSTACK_TRANSFORMATION_LIST_ALL_LIBRARIES` | List All Libraries | Tool to retrieve all published libraries for a workspace. Use when you need to list available libraries for transformations. |
| `RUDDERSTACK_TRANSFORMATION_LIST_LIBRARY_VERSIONS` | List Library Versions | Tool to get all library revisions for a library ID. Use when you need to retrieve all versions of a specific library in RudderStack Transformation. |
| `RUDDERSTACK_TRANSFORMATION_LIST_ALL_TRANSFORMATIONS` | List All Transformations | Tool to retrieve all published transformations for a workspace. Use when you need to list available transformations or find a specific transformation by name. |
| `RUDDERSTACK_TRANSFORMATION_LIST_TRANSFORMATION_VERSIONS` | List Transformation Versions | Tool to list all transformation versions (revisions) for a given transformation ID. Use when you need to retrieve the version history of a specific transformation. |
| `RUDDERSTACK_TRANSFORMATION_UPDATE_TRANSFORMATION` | Update Transformation | Tool to update and optionally publish a RudderStack transformation. Use when you need to modify a transformation's name, description, or code. Updating creates a new revision and sets it as published if the publish flag is true. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The RudderStack Transformation MCP server is an implementation of the Model Context Protocol that connects your AI agent to RudderStack Transformation. It provides structured and secure access so your agent can perform RudderStack Transformation operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A RudderStack Transformation connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to RudderStack Transformation via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived RudderStack Transformation MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for RudderStack Transformation

**What's happening:**
- You create a RudderStack Transformation only session through Composio
- Composio returns an MCP HTTP URL that exposes RudderStack Transformation tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["rudderstack_transformation"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["rudderstack_transformation"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to RudderStack Transformation through Composio's Tool Router. The agent can perform RudderStack Transformation operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build RudderStack Transformation MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/rudderstack_transformation/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/rudderstack_transformation/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/rudderstack_transformation/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/rudderstack_transformation/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/rudderstack_transformation/framework/cli)
- [Google ADK](https://composio.dev/toolkits/rudderstack_transformation/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/rudderstack_transformation/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/rudderstack_transformation/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/rudderstack_transformation/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/rudderstack_transformation/framework/llama-index)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Firecrawl](https://composio.dev/toolkits/firecrawl) - Firecrawl automates large-scale web crawling and data extraction. It helps organizations efficiently gather, index, and analyze content from online sources.
- [Tavily](https://composio.dev/toolkits/tavily) - Tavily offers powerful search and data retrieval from documents, databases, and the web. It helps teams locate and filter information instantly, saving hours on research.
- [Exa](https://composio.dev/toolkits/exa) - Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows.
- [Serpapi](https://composio.dev/toolkits/serpapi) - SerpApi is a real-time API for structured search engine results. It lets you automate SERP data collection, parsing, and analysis for SEO and research.
- [Peopledatalabs](https://composio.dev/toolkits/peopledatalabs) - Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data.
- [Snowflake](https://composio.dev/toolkits/snowflake) - Snowflake is a cloud data warehouse built for elastic scaling, secure data sharing, and fast SQL analytics across major clouds.
- [Posthog](https://composio.dev/toolkits/posthog) - PostHog is an open-source analytics platform for tracking user interactions and product metrics. It helps teams refine features, analyze funnels, and reduce churn with actionable insights.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Amplitude](https://composio.dev/toolkits/amplitude) - Amplitude is a digital analytics platform for product and behavioral data insights. It helps teams analyze user journeys and make data-driven decisions quickly.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and RudderStack Transformation MCP?

With a standalone RudderStack Transformation MCP server, the agents and LLMs can only access a fixed set of RudderStack Transformation tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from RudderStack Transformation and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right RudderStack Transformation tools.

### Can I manage the permissions and scopes for RudderStack Transformation while using Tool Router?

Yes, absolutely. You can configure which RudderStack Transformation scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your RudderStack Transformation data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
