How to integrate Ipdata co MCP with Pydantic AI

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

Introduction

This guide walks you through connecting Ipdata co to Pydantic AI 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 Pydantic AI 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:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Ipdata co
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Ipdata co workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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 with an active API key
  • Basic familiarity with Python and async programming

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 pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Ipdata co
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file

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

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Ipdata co
  • MCPServerStreamableHTTP connects to the Ipdata co MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Ipdata co
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["ipdata_co"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Ipdata co tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
ipdata_co_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[ipdata_co_mcp],
    instructions=(
        "You are a Ipdata co assistant. Use Ipdata co tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Ipdata co endpoint
  • The agent uses GPT-5 to interpret user commands and perform Ipdata co operations
  • The instructions field defines the agent's role and behavior

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Ipdata co.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Ipdata co API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

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

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Ipdata co
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["ipdata_co"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    ipdata_co_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[ipdata_co_mcp],
        instructions=(
            "You are a Ipdata co assistant. Use Ipdata co tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Ipdata co.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with Ipdata co through Composio's Tool Router. With this setup, your agent can perform real Ipdata co actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Ipdata co for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

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

CrewAI

CrewAI

Use Ipdata co MCP with CrewAI

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 Pydantic AI?

Yes, you can. Pydantic AI 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