How to integrate Ipdata co MCP with CrewAI

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

Introduction

This guide walks you through connecting Ipdata co to CrewAI using the Composio tool router. By the end, you'll have a working Ipdata co agent that can get city and country for this ip address, check if this ip is from the eu, find mobile carrier for a given ip, show my api usage count for today through natural language commands.

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

The Ipdata co MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ipdata co account. It provides structured and secure access to IP geolocation, carrier, and threat intelligence data, so your agent can perform actions like IP lookups, ASN analysis, carrier identification, and usage monitoring on your behalf.

  • Comprehensive IP lookups: Instantly retrieve detailed location, ownership, and threat profile information for any IP address worldwide.
  • Advanced ASN intelligence: Dive deep into network data by performing advanced ASN lookups to get prefixes, peer relationships, and registry details for a given ASN number.
  • Carrier and telecom insights: Fetch mobile carrier data—including carrier name, MCC, and MNC—for specific IPs to help identify network providers or mobile origins.
  • EU-specific IP processing: Ensure data residency compliance by performing IP lookups processed and stored exclusively within the EU.
  • API usage monitoring: Easily check your API request counts from the last 24 hours to stay on top of your Ipdata co usage and quotas.

Supported Tools & Triggers

Tools
Advanced ASN LookupTool to perform advanced ASN lookup returning prefixes, peers, and registry details.
Get Carrier Data for an IPTool to return mobile carrier data for a specific IP.
EU-specific IP lookupTool to lookup a specific IP address via the EU-only data residency endpoint.
IPData: Calling CodeTool to fetch the international calling_code for an IP's country.
IPDATA Field CarrierTool to return only the carrier object for the calling IP.
Get City from IPTool to return only city for an IP.
IPData: Continent CodeTool to return only continent_code for an IP.
Get Continent Name from IPTool to return only continent name for an IP.
IPDATA Field CountTool to return only the request count made by your API key in the last 24 hours.
IPData: Country CodeTool to return only country_code for an IP.
Get Country Name from IPTool to return only country name for an IP.
IPDATA Field CurrencyTool to return only currency object for an IP.
Get Emoji Flag from IPTool to return only emoji flag for an IP.
Get Emoji Unicode from IPTool to return only emoji_unicode for an IP.
IPData: IPTool to return only the caller’s IP string.
IPData: Is EUTool to return only is_eu for an IP.
IPData: LanguagesTool to return only the languages array for an IP.
IPData: LatitudeTool to return only the latitude for an IP.
Get Longitude from IPTool to return only longitude for an IP.
IPData: Postal CodeTool to return only postal code for an IP.
Get Region from IPTool to return only region for an IP.
IPData: Region CodeTool to return only region_code for an IP.
Get Threat for IPTool to return only the threat object for the calling IP.
IPData: Time ZoneTool to return only the time_zone object for an IP.
Get Currency for IPTool to retrieve currency information for a specific IP.
IPData Basic ASN for IPTool to return basic ASN data for a specific IP.
IPData Bulk Lookup V1Tool to bulk lookup up to 100 IP addresses via ipdata.
Get company data for IPTool to retrieve company data for a given IP address.
EU-only calling IP lookupTool to lookup the calling client IP via EU-residency endpoint.
IPData Lookup IP V1Tool to lookup comprehensive IP information (geolocation, network, company, and threat data) in one call.
IPData Threat for IPTool to return threat intelligence data for a specific IP.
IPData Time Zone for IPTool to return timezone data for a specific IP.
Lookup Calling IPTool to lookup full data for the calling client IP.

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 Ipdata co 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 Ipdata co 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 Ipdata co MCP URL

Create a Composio Tool Router session for Ipdata co

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["ipdata_co"],
)
url = session.mcp.url
What's happening:
  • You create a Ipdata co only session through Composio
  • Composio returns an MCP HTTP URL that exposes Ipdata co 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="Ipdata co Assistant",
    goal="Help users interact with Ipdata co through natural language commands",
    backstory=(
        "You are an expert assistant with access to Ipdata co tools. "
        "You can perform various Ipdata co 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 Ipdata co 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 Ipdata co 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 Ipdata co 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_ipdata_co_agent.py

Complete Code

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

python
# file: crewai_ipdata_co_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 Ipdata co session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["ipdata_co"],
    )
    url = session.mcp.url

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

    # Create Ipdata co assistant agent
    toolkit_agent = Agent(
        role="Ipdata co Assistant",
        goal="Help users interact with Ipdata co through natural language commands",
        backstory=(
            "You are an expert assistant with access to Ipdata co tools. "
            "You can perform various Ipdata co 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 Ipdata co 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 Ipdata co 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 Ipdata co through Composio's Tool Router. The agent can perform Ipdata co 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 Ipdata co MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Ipdata co MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Ipdata co MCP with Claude Agent SDK

Google ADK

Google ADK

Use Ipdata co MCP with Google ADK

LangChain

LangChain

Use Ipdata co MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Ipdata co MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Ipdata co MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Ipdata co MCP with LlamaIndex

FAQ

What are the differences in Tool Router MCP and Ipdata co MCP?

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

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

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