How to integrate Realphonevalidation MCP with CrewAI

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

Introduction

This guide walks you through connecting Realphonevalidation to CrewAI using the Composio tool router. By the end, you'll have a working Realphonevalidation agent that can check if this phone number is active, validate if a number is wireless or landline, verify if this email address is disposable, bulk scrub these phone numbers for validity through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Realphonevalidation account through Composio's Realphonevalidation 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 Realphonevalidation connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Realphonevalidation
  • Build a conversational loop where your agent can execute Realphonevalidation 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 Realphonevalidation MCP server, and what's possible with it?

The Realphonevalidation MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Realphonevalidation account. It provides structured and secure access to advanced phone number and email verification services, so your agent can perform actions like real-time phone validation, carrier checks, bulk number scrubbing, and email deliverability checks on your behalf.

  • Instant phone number validation: Let your agent verify if a phone number is active, its type (mobile or landline), carrier, and caller details in real time.
  • Bulk number scrubbing: Automatically process and validate large lists of phone numbers, checking for connectivity and type to ensure data accuracy at scale.
  • Email address verification: Have your agent check if an email is deliverable and not disposable, helping prevent bouncebacks and spam risks.
  • Reassigned and consent compliance checks: Enable your agent to determine if a number has been reassigned since a specific consent date for regulatory compliance.
  • Carrier and wireless identification: Easily identify whether a US phone number is wireless or landline for TCPA compliance and segmentation.

Supported Tools & Triggers

Tools
Email VerificationTool to validate an email address and check connectivity and disposability.
Check Phone Active StatusTool to determine if a phone number is active on a valid phone service provider.
Reassigned Number LookupTool to check if a phone number has been reassigned since a given consent date.
Scrub Plus Phone NumbersTool to scrub phone numbers in bulk for connection status and type.
RPV Turbo V3 Phone ValidationTool to perform real-time phone number validation (status, type, carrier, caller name/type).
Wireless IDTool to identify whether a us phone number is landline or wireless.

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 Realphonevalidation 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 python-dotenv
What's happening:
  • composio connects your agent to Realphonevalidation via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools 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
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional import if you plan to adapt tools
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()
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 Realphonevalidation MCP URL

Create a Composio Tool Router session for Realphonevalidation

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["realphonevalidation"],
)
url = session.mcp.url
What's happening:
  • You create a Realphonevalidation only session through Composio
  • Composio returns an MCP HTTP URL that exposes Realphonevalidation tools

Configure the LLM

python
llm = LLM(
    model="gpt-5-mini",
    api_key=os.getenv("OPENAI_API_KEY"),
)
What's happening:
  • CrewAI will call this LLM for planning and responses
  • You can swap in a different model if needed

Attach the MCP server and create the agent

python
toolkit_agent = Agent(
    role="Realphonevalidation Assistant",
    goal="Help users interact with Realphonevalidation through natural language commands",
    backstory=(
        "You are an expert assistant with access to Realphonevalidation tools. "
        "You can perform various Realphonevalidation operations on behalf of the user."
    ),
    mcps=[
        MCPServerHTTP(
            url=url,
            streamable=True,
            cache_tools_list=True,
            headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
        ),
    ],
    llm=llm,
    verbose=True,
    max_iter=10,
)
What's happening:
  • MCPServerHTTP connects the agent to the Realphonevalidation MCP endpoint
  • cache_tools_list saves a tools catalog for faster subsequent runs
  • verbose helps you see what the agent is doing

Add a REPL loop with Task and Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to perform Realphonevalidation operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
            f"Current user request: {user_input}\n\n"
            f"Please help the user with their Realphonevalidation related request."
        ),
        expected_output="A helpful response addressing the user's request",
        agent=toolkit_agent,
    )

    crew = Crew(
        agents=[toolkit_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:
  • You build a simple chat loop and keep a running context
  • Each user turn becomes a Task handled by the same agent
  • Crew executes the task and returns a response

Run the application

python
if __name__ == "__main__":
    main()
What's happening:
  • Standard Python entry point so you can run python crewai_realphonevalidation_agent.py

Complete Code

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

python
# file: crewai_realphonevalidation_agent.py
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()

def main():
    # Initialize Composio and create a Realphonevalidation session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["realphonevalidation"],
    )
    url = session.mcp.url

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

    # Create Realphonevalidation assistant agent
    toolkit_agent = Agent(
        role="Realphonevalidation Assistant",
        goal="Help users interact with Realphonevalidation through natural language commands",
        backstory=(
            "You are an expert assistant with access to Realphonevalidation tools. "
            "You can perform various Realphonevalidation operations on behalf of the user."
        ),
        mcps=[
            MCPServerHTTP(
                url=url,
                streamable=True,
                cache_tools_list=True,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
            ),
        ],
        llm=llm,
        verbose=True,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Try asking the agent to perform Realphonevalidation operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
                f"Current user request: {user_input}\n\n"
                f"Please help the user with their Realphonevalidation related request."
            ),
            expected_output="A helpful response addressing the user's request",
            agent=toolkit_agent,
        )

        crew = Crew(
            agents=[toolkit_agent],
            tasks=[task],
            verbose=False,
        )

        result = crew.kickoff()
        response = str(result)

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

if __name__ == "__main__":
    main()

Conclusion

You now have a CrewAI agent connected to Realphonevalidation through Composio's Tool Router. The agent can perform Realphonevalidation 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 Realphonevalidation MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Realphonevalidation MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Realphonevalidation MCP with Claude Agent SDK

Google ADK

Google ADK

Use Realphonevalidation MCP with Google ADK

LangChain

LangChain

Use Realphonevalidation MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Realphonevalidation MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Realphonevalidation MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Realphonevalidation MCP with LlamaIndex

FAQ

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

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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