# How to integrate Pipeline crm MCP with CrewAI

```json
{
  "title": "How to integrate Pipeline crm MCP with CrewAI",
  "toolkit": "Pipeline crm",
  "toolkit_slug": "pipeline_crm",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/pipeline_crm/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/pipeline_crm/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:22:07.384Z"
}
```

## Introduction

This guide walks you through connecting Pipeline crm to CrewAI using the Composio tool router. By the end, you'll have a working Pipeline crm agent that can list all leads added this week, get details for deal with id 789, delete company with id 123 through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Pipeline crm account through Composio's Pipeline crm MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Pipeline crm with

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

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Pipeline crm connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Pipeline crm
- Build a conversational loop where your agent can execute Pipeline crm 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 Pipeline crm MCP server, and what's possible with it?

The Pipeline crm MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Pipeline crm account. It provides structured and secure access to your sales pipeline data, so your agent can perform actions like tracking leads, managing deals, updating company information, organizing tasks, and streamlining sales workflows on your behalf.
- Lead and company management: Effortlessly list, retrieve, or delete companies and leads, making it easy to keep your CRM up to date and focused on the right opportunities.
- Deal tracking and stage management: Let your agent fetch deal details, monitor deal stages, or remove outdated deals to ensure your pipeline always reflects current sales activity.
- Calendar task organization: Automatically list and retrieve calendar tasks, or pull specific task details by ID to stay on top of follow-ups and scheduled activities.
- Comprehensive sales workflow automation: Ask your agent to enumerate deal stages, manage associated tasks, and streamline repetitive CRM operations so your team can focus on closing more deals.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PIPELINE_CRM_CREATE_COMPANY` | Create Pipeline CRM Company | Creates a new company record in Pipeline CRM with contact details, address, and social media information. Use this tool when you need to add a new company to the CRM system. The only required field is the company name. You can optionally include contact information (email, phone, fax), address details, social media links, and assign owners or tags. Set check_for_duplicates=true to prevent creating companies with duplicate names. |
| `PIPELINE_CRM_CREATE_DEAL` | Create Deal | Tool to create a new deal in Pipeline CRM. Use after gathering all details. Example: Create a deal named 'Big Partnership' worth 50000 USD in stage 2. |
| `PIPELINE_CRM_DELETE_COMPANY` | Delete Company | Tool to delete a company by ID in Pipeline CRM. Use after confirming the company ID is correct. Example: "Delete company with ID 123". |
| `PIPELINE_CRM_DELETE_DEAL` | Delete Deal | Tool to delete a deal by ID. Use when you need to remove a deal from Pipeline CRM. |
| `PIPELINE_CRM_DELETE_TASK` | Delete calendar task | Tool to delete a calendar task by ID. Use after confirming the task exists in Pipeline CRM. |
| `PIPELINE_CRM_GET_COMPANY` | Get Company by ID | Retrieves comprehensive details for a specific company by ID from Pipeline CRM. Returns complete company information including contact details (multiple phones, email, social media), full address breakdown, owner details, financial metrics (pipeline/won deals totals), custom fields, tags, and next scheduled tasks. Use this when you need detailed information about a company after obtaining its ID from LIST_COMPANIES or CREATE_COMPANY actions. |
| `PIPELINE_CRM_GET_DEAL` | Get Deal by ID | Tool to retrieve details for a specific deal by ID in Pipeline CRM. Use after confirming the deal ID. |
| `PIPELINE_CRM_GET_STAGE` | Get Deal Stage by ID | Tool to retrieve details for a specific stage by ID in Pipeline CRM. Use after confirming the stage ID. |
| `PIPELINE_CRM_GET_TASK` | Get calendar task by ID | Tool to retrieve details for a specific task by ID in Pipeline CRM. Use after confirming the task ID. |
| `PIPELINE_CRM_LIST_COMPANIES` | List Companies | List companies in Pipeline CRM with optional filtering, sorting, and pagination. Returns a paginated list of companies with comprehensive details including contact information, address, owner, custom fields, and tags. Supports search filtering and sorting by any field. Use this to retrieve multiple companies or search for specific companies by name or other attributes. |
| `PIPELINE_CRM_LIST_LEADS` | List Leads | Tool to list leads in Pipeline CRM. Use when you need to fetch multiple leads with optional filtering and pagination. For large datasets, iterate through pages using `page` and `per_page` together; a single `per_page` value does not return all leads. |
| `PIPELINE_CRM_LIST_STAGES` | List Deal Stages | Tool to list deal stages. Use when you need to enumerate all stages for deals in Pipeline CRM. |
| `PIPELINE_CRM_LIST_TASKS` | List calendar tasks | Tool to list calendar tasks. Use when retrieving tasks for a deal, company, or person with optional date filters and pagination. |
| `PIPELINE_CRM_LIST_USERS` | List Users | List users in Pipeline CRM account with optional pagination. Returns a paginated list of users with their details including email, name, role, status, and admin privileges. Use this to retrieve user information for assignment, reporting, or user management purposes. For large accounts, iterate through pages using `page` and `per_page` parameters. Requires admin access to the API. |
| `PIPELINE_CRM_UPDATE_COMPANY` | Update Company | Tool to update an existing company by ID in Pipeline CRM. Use after confirming the company ID and fields to change. |

## Supported Triggers

None listed.

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

The Pipeline crm MCP server is an implementation of the Model Context Protocol that connects your AI agent to Pipeline crm. It provides structured and secure access so your agent can perform Pipeline crm 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 Pipeline crm 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 Pipeline crm 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 Pipeline crm 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 Pipeline crm

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

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=["pipeline_crm"],
)
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 Pipeline crm through Composio's Tool Router. The agent can perform Pipeline crm 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 Pipeline crm MCP Agent with another framework

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

## Related Toolkits

- [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.
- [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.
- [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place.
- [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently.
- [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities.
- [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place.
- [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources.
- [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations.
- [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface.
- [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently.
- [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools.
- [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data.
- [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place.
- [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process.
- [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Pipeline crm MCP?

With a standalone Pipeline crm MCP server, the agents and LLMs can only access a fixed set of Pipeline crm tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Pipeline crm 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 Pipeline crm tools.

### Can I manage the permissions and scopes for Pipeline crm while using Tool Router?

Yes, absolutely. You can configure which Pipeline crm 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 Pipeline crm data and credentials are handled as safely as possible.

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