How to integrate Extrovert MCP with CrewAI

This guide walks you through connecting Extrovert to CrewAI using the Composio tool router. By the end, you'll have a working Extrovert agent that can find linkedin prospects, list your campaigns, manage writing styles, manage contexts, and view plan features through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Extrovert account through Composio's Extrovert MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Extrovert logoExtrovert
Api Key

Extrovert is a LinkedIn prospect engagement platform for campaigns, monitored topics, writing styles, contexts, and team workflows. It helps teams scale relevant outreach while keeping prospect conversations organized.

15 Tools

Introduction

This guide walks you through connecting Extrovert to CrewAI using the Composio tool router. By the end, you'll have a working Extrovert agent that can find linkedin prospects, list your campaigns, manage writing styles, manage contexts, and view plan features through natural language commands.

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

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

Also integrate Extrovert with

TL;DR

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

The Extrovert MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Extrovert account. It provides structured and secure access to your campaigns, prospects, writing styles, engagement contexts, team, and workspace plan, so your agent can review campaigns, find prospects, manage messaging guidance, inspect team members, and check plan capabilities on your behalf.

  • Campaign monitoring: Have your agent list prospect and topic campaigns, then review their status, filters, automation settings, owners, and sharing configuration.
  • Prospect research: Let the agent browse prospects, inspect LinkedIn profile and engagement details, or check whether a LinkedIn profile already exists in your team's records.
  • Engagement context management: Direct your agent to create, review, update, or delete company and user background contexts used to guide prospect engagement.
  • Writing style management: Instruct your agent to create, review, update, or remove writing styles for LinkedIn comments and direct messages.
  • Team and plan visibility: Have your agent review visible team members and check your workspace plan, available features, API capabilities, and quota usage.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step08 STEPS
1

Prerequisites

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

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.
3

Install dependencies

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

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
5

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 Extrovert MCP URL
6

Create a Composio Tool Router session for Extrovert

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

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

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.
8

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 Extrovert and CrewAI:

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=["extrovert"],
)
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 Extrovert through Composio's Tool Router. The agent can perform Extrovert 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
TOOLS

Supported Tools

Every Extrovert action and event your agent gets out of the box.

Create Context

Create a Context for a user.

Create Style

Create a writing Style for a user.

Delete Context

Permanently delete one Context by UUID.

Delete Style

Permanently delete one Style by UUID.

Find Prospect by LinkedIn URL

Check whether a LinkedIn profile URL already exists among the team's prospects and return every matching prospect.

Get Campaign

Load full configuration and state for one campaign by its UUID.

Get Prospect

Load one existing prospect by UUID with LinkedIn profile, campaign and list bindings, flags, connection data, and engagement statistics.

Get Workspace Plan Features

Return the selected workspace's active plan, API capabilities, feature flags, and quota counters.

List Campaigns

Return all Prospects and Topic campaigns visible to the connected user, including their running state, owner, Context, Style, filters, automation, and sharing configuration.

List Contexts

Return all complete Context records owned by a user.

List Prospects

Return one page of existing prospects with campaign and list bindings, LinkedIn profile data, flags, connection state, and engagement statistics.

List Styles

Return all complete writing Styles owned by a user, including learning mode and separate comment and direct-message instructions.

List Team Members

Return users visible in the selected team, including the user IDs required to list or create owner-scoped contexts and styles.

Update Context

Fully replace a Context's name, company background, and user background.

Update Style

Update a Style's required name and learning-mode setting, optionally replacing or clearing its comment and DM instructions.

FAQ

Frequently asked questions

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

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 Extrovert tools.

Yes, absolutely. You can configure which Extrovert 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.

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 Extrovert data and credentials are handled as safely as possible.

Start with Extrovert.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Extrovert tool your agent needs.Free to start.

Start building