SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Ipdata co MCP with CrewAI

Connect CrewAI to Ipdata co MCP. Get city and country for this ip address, check if this ip is from the eu, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Ipdata co logoIpdata co
Api Key

Ipdata co is an API service that provides detailed geolocation, ownership, and threat insights for any IP address. Use it to instantly identify, analyze, and assess the risk profile of IPs in your applications.

28 Tools

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 geolocate IP addresses, check threat data, look up ASN and carrier details, run bulk lookups, and identify companies 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.

Also integrate Ipdata co with

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

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.

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

Create a Composio Tool Router session for Ipdata co

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_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
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 Ipdata co 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=["ipdata_co"],
)
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 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
TOOLS

Supported Tools

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

Advanced ASN Lookup

Tool to perform advanced ASN lookup returning prefixes, peers, and registry details.

EU IP Lookup (Specific IP)

Lookup geolocation, threat intel, and network data for a specific IP address using the EU data residency endpoint.

IPData: Calling Code

Tool to fetch the international calling_code for an IP's country.

IPDATA Field Carrier

Retrieve mobile carrier information (name, MCC, MNC) for an IP address.

Get City from IP

Tool to return only city for an IP.

IPData: Continent Code

Retrieve the continent code for a given IP address.

Get Continent Name from IP

Tool to return only continent name for an IP.

IPDATA Field Count

Tool to return only the request count made by your API key in the last 24 hours.

IPData: Country Code

Tool to return only country_code for an IP.

Get Country Name from IP

Get the country name for an IP address using ipdata.

IPDATA Field Currency

Tool to return only currency object for an IP.

Get Emoji Flag from IP

Tool to return only emoji flag for an IP.

Get Emoji Unicode from IP

Tool to return only emoji_unicode for an IP.

IPData: IP

Retrieve the public IP address seen by IPData for the server making the API request.

IPData: Is EU

Tool to return only is_eu for an IP.

IPData: Languages

Tool to return only the languages array for an IP.

IPData: Latitude

Tool to return only the latitude for an IP.

Get Longitude from IP

Tool to return only longitude for an IP.

IPData: Postal Code

Tool to return only postal code for an IP.

Get Region from IP

Tool to return only region for an IP.

IPData: Region Code

Tool to return only region_code for an IP.

Get Threat for IP

Retrieve threat intelligence data for a specific IP address or the calling IP.

IPData: Time Zone

Tool to return only the time_zone object for an IP.

IPData Basic ASN for IP

Tool to return basic ASN data for a specific IP.

IPData Bulk Lookup V1

Looks up 1–100 IPv4 or IPv6 addresses with ipdata for geolocation, network, and threat information.

Get company data for IP

Tool to retrieve company data for a given IP address.

EU IP Lookup (Calling IP)

Lookup geolocation, network, and threat data for the calling client's IP address using the EU-residency endpoint.

IPData Lookup IP V1

Tool to lookup comprehensive IP information (geolocation, network, company, and threat data) in one call.

FRAMEWORKS

How to build Ipdata co MCP Agent with another framework

Claude Code logo

Claude Code

Use Ipdata co MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Ipdata co MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ipdata co MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ipdata co MCP with Claude Agent SDK

Codex logo

Codex

Use Ipdata co MCP with Codex

OpenClaw logo

OpenClaw

Use Ipdata co MCP with OpenClaw

Hermes logo

Hermes

Use Ipdata co MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Ipdata co MCP with Atomic Agent

Google ADK logo

Google ADK

Use Ipdata co MCP with Google ADK

LangChain logo

LangChain

Use Ipdata co MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Ipdata co MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Ipdata co MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ipdata co MCP with LlamaIndex

Pydantic AI logo

Pydantic AI

Use Ipdata co MCP with Pydantic AI

AutoGen logo

AutoGen

Use Ipdata co MCP with AutoGen

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Ipdata co.It takes 30 seconds.

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

Start building