How to integrate Centralstationcrm MCP with CrewAI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Centralstationcrm Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Centralstationcrm to CrewAI using the Composio tool router. By the end, you'll have a working Centralstationcrm agent that can add new company to crm contacts, log a sales opportunity for a client, count total people in my crm, record a birthday for an existing contact through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Centralstationcrm account through Composio's Centralstationcrm MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

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

The Centralstationcrm MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Centralstationcrm account. It provides structured and secure access to your customer relationship data, so your agent can perform actions like managing contacts, creating deals, updating company records, and tracking key interactions on your behalf.

  • Automated contact management: Quickly add new people to your CRM, update their details, and ensure your contact database stays current without manual entry.
  • Company and organization creation: Effortlessly create new company records so you can keep your account-based selling and organization tracking up-to-date.
  • Deal tracking and creation: Instantly log new sales opportunities by creating deals linked to your contacts or companies, helping your team stay on top of the pipeline.
  • Detailed relationship enrichment: Add addresses, assistants, avatars, and contact details to people in your CRM, making every customer profile richer and more actionable.
  • Milestone and history recording: Record important life events or milestones (like birthdays or anniversaries) for each person to boost relationship management and personalized outreach.

Supported Tools & Triggers

Tools
Check ConnectionTool to verify the connection status of the centralstationcrm api key.
Count PeopleTool to retrieve the total number of people in the account.
Create CompanyTool to create a new company record.
Create DealTool to create a new deal record.
Create PersonTool to create a new person record.
Create Person AddressTool to create a new address for a specific person.
Create Person AssistantTool to create a new assistant (assi) entry for a specific person.
Create Person AvatarTool to create a new avatar for a specific person.
Create Person Contact DetailTool to create a new contact detail for a specific person.
Create Person Historic EventTool to create a new historic event for a specific person.
Delete CompanyTool to delete a company record by id.
Delete personTool to delete a person record by id.
Delete Person AddressTool to delete a person's address by its id.
Delete Person AssiTool to delete an assi entry of a person.
Delete Person AvatarTool to delete a person's avatar by its id.
Delete Person Contact DetailTool to delete a contact detail of a person.
Delete Person Historic EventTool to delete a historic event of a person by its id.
Get API User MaildropTool to retrieve the current api user's maildrop for people and companies.
Get CompanyTool to retrieve details of a specific company by id.
Get DealTool to retrieve details of a specific deal by its id.
Get DealsTool to retrieve a paginated list of all deals.
Get PersonTool to retrieve details of a specific person by id.
Get Person AddressTool to retrieve a specific address of a person by address id.
Get Person AddressesTool to retrieve all addresses for a specific person.
Get Person AssiTool to retrieve a specific assi entry of a person by id.
Get Person AssisTool to retrieve all assistant entries for a specific person.
Get Person AvatarTool to retrieve a specific avatar of a person by avatar id.
Get Person AvatarsTool to retrieve all avatars for a specific person.
Get Person Contact DetailTool to retrieve a specific contact detail by id for a person.
Get Person Custom FieldsTool to retrieve all custom fields for a specific person.
Get Person Historic EventTool to retrieve a specific historic event of a person by id.
Get Person Historic EventsTool to retrieve all historic events for a specific person.
Get PersonsTool to retrieve a paginated list of all people.
Merge PersonTool to merge another person into an existing person by id.
Search RecordsSearch records
Search PeopleTool to retrieve people matching search criteria.
Stats PeopleTool to retrieve key statistics about people.
Update CompanyTool to update an existing company by id.
Update PersonTool to update an existing person by id.
Update Person AddressTool to update a specific address of a person.
Update Person AssiTool to update an assi entry of a person.
Update Person Contact DetailTool to update a specific contact detail of a person by id.
Update Person Historic EventTool to update a historic event of a person by id.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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

Import dependencies

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")
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 Centralstationcrm MCP URL

Create a Composio Tool Router session for Centralstationcrm

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["centralstationcrm"])

url = session.mcp.url
What's happening:
  • You create a Centralstationcrm only session through Composio
  • Composio returns an MCP HTTP URL that exposes Centralstationcrm tools

Initialize the MCP Server

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,
    )
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.

Create a CLI Chatloop and define the Crew

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")
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.

Complete Code

Here's the complete code to get you started with Centralstationcrm and CrewAI:

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

OpenAI Agents SDK

OpenAI Agents SDK

Use Centralstationcrm MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Centralstationcrm MCP with Claude Agent SDK

Google ADK

Google ADK

Use Centralstationcrm MCP with Google ADK

LangChain

LangChain

Use Centralstationcrm MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Centralstationcrm MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Centralstationcrm MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Centralstationcrm MCP with LlamaIndex

FAQ

What are the differences in Tool Router MCP and Centralstationcrm MCP?

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

Can I manage the permissions and scopes for Centralstationcrm while using Tool Router?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free