SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Findymail MCP with CrewAI

Connect CrewAI to Findymail MCP. Find verified email for john at acme.com, create a new contact list for leads, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Findymail logoFindymail
Api Key

Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.

21 Tools

Introduction

This guide walks you through connecting Findymail to CrewAI using the Composio tool router. By the end, you'll have a working Findymail agent that can find emails by name, verify emails, manage contact and exclusion lists, search Intellimatch, and check your credits through natural language commands.

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

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

Also integrate Findymail with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexPydantic AIAutoGen

TL;DR

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

The Findymail MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Findymail account. It provides structured and secure access to verified B2B contact data, so your agent can create and manage contact lists, find and verify emails, and streamline your outreach workflow automatically.

  • Automated contact list management: Let your agent create new contact lists, fetch all your lists, or delete lists as your prospecting needs change.
  • Precise contact discovery: Ask your agent to find and retrieve emails for prospects based on full name and company domain, making it easier to build targeted outreach campaigns.
  • Bulk contact retrieval: Direct your agent to list all contacts within a specific list, enabling quick access to leads for export or follow-up.
  • Email deliverability verification: Have your agent check if an email address is valid and safe to use before sending that crucial first message.
  • Seamless CRM enrichment: Use verified contact details to automatically enrich your CRM, helping you keep data accurate and actionable for your sales team.

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

Create a Composio Tool Router session for Findymail

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

url = session.mcp.url
What's happening:
  • You create a Findymail only session through Composio
  • Composio returns an MCP HTTP URL that exposes Findymail 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 Findymail 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=["findymail"],
)
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 Findymail through Composio's Tool Router. The agent can perform Findymail 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 Findymail action and event your agent gets out of the box.

Add Excluded Domain

Add domains to Findymail exclusions used by Intellimatch searches.

Create Exclusion List

Create a named exclusion list for the authenticated user to organize websites excluded from Intellimatch searches.

Create Contact List

Tool to create a new contact list.

Delete Exclusion List

Delete an Intellimatch exclusion list by ID and all its associated domains.

Delete Contact List

Permanently deletes a contact list by its ID.

Find Email by Name

Find a person's email using their full name and company domain or company name.

Get Contact Lists

Tool to retrieve all contact lists.

Get Credits

Check the team's remaining Findymail credit balance before running operations.

Get Credits Summary

Tool to retrieve credits usage summary report for the authenticated account.

Get Credits Team Summary

Retrieve the team's credit usage summary for the default reporting period, including totals and usage by team member.

Get Exclusion List

Retrieve metadata for an exclusion list by ID, without its domains.

Get Intellimatch Data

Retrieve the default first page of company data from a completed Intellimatch search by hash.

Get Intellimatch Status

Tool to check the status of an Intellimatch search job.

List Contacts

Tool to retrieve contacts from a specified list (paginated).

List Excluded Domains

Retrieve a page of globally excluded domains for Intellimatch searches.

List Exclusion Lists

Tool to retrieve all exclusion lists for managing excluded websites from Intellimatch searches.

Remove Excluded Domain

Remove excluded domains by ID from Intellimatch exclusion lists.

Search Intellimatch

Start an Intellimatch company search using a natural-language query, optionally finding contacts and emails.

Update Exclusion List

Rename an existing exclusion list.

Update Contact List

Update an existing Findymail contact list's name and team-sharing setting.

Verify Email

Verify the deliverability of an email address before outreach.

FRAMEWORKS

How to build Findymail MCP Agent with another framework

Claude Code logo

Claude Code

Use Findymail MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Findymail MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Findymail MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Findymail MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Findymail MCP with Grok Bot

Codex logo

Codex

Use Findymail MCP with Codex

OpenClaw logo

OpenClaw

Use Findymail MCP with OpenClaw

Hermes logo

Hermes

Use Findymail MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Findymail MCP with Atomic Agent

Google ADK logo

Google ADK

Use Findymail MCP with Google ADK

LangChain logo

LangChain

Use Findymail MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Findymail MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Findymail MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Findymail MCP with LlamaIndex

Pydantic AI logo

Pydantic AI

Use Findymail MCP with Pydantic AI

AutoGen logo

AutoGen

Use Findymail MCP with AutoGen

FAQ

Frequently asked questions

Start with Findymail.It takes 30 seconds.

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

Start building