# How to integrate Ipdata co MCP with Pydantic AI ```json { "title": "How to integrate Ipdata co MCP with Pydantic AI", "toolkit": "Ipdata co", "toolkit_slug": "ipdata_co", "framework": "Pydantic AI", "framework_slug": "pydantic-ai", "url": "https://composio.dev/toolkits/ipdata_co/framework/pydantic-ai", "markdown_url": "https://composio.dev/toolkits/ipdata_co/framework/pydantic-ai.md", "updated_at": "2026-05-12T10:16:18.761Z" } ``` ## 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 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. ## Also integrate Ipdata co with - [OpenAI Agents SDK](https://composio.dev/toolkits/ipdata_co/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ipdata_co/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ipdata_co/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ipdata_co/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ipdata_co/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ipdata_co/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ipdata_co/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ipdata_co/framework/cli) - [Google ADK](https://composio.dev/toolkits/ipdata_co/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ipdata_co/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ipdata_co/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ipdata_co/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ipdata_co/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ipdata_co/framework/crew-ai) ## 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 | Tool slug | Name | Description | |---|---|---| | `IPDATA_CO_ADVANCED_ASN_LOOKUP` | Advanced ASN Lookup | Tool to perform advanced ASN lookup returning prefixes, peers, and registry details. Use after confirming ASN number when detailed ASN info is required. | | `IPDATA_CO_EU_LOOKUP_SPECIFIC_IP` | EU IP Lookup (Specific IP) | Lookup geolocation, threat intel, and network data for a specific IP address using the EU data residency endpoint. Use this tool when: - You need IP lookup with GDPR compliance (data processed and stored only within EU datacenters) - Looking up any IPv4 or IPv6 address for location, ASN, threat, or company information The EU endpoint (eu-api.ipdata.co) ensures all API requests are routed through EU-based servers in Frankfurt, Paris, and Ireland. | | `IPDATA_CO_FIELD_CALLING_CODE` | IPData: Calling Code | Tool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co. | | `IPDATA_CO_FIELD_CARRIER` | IPDATA Field Carrier | Retrieve mobile carrier information (name, MCC, MNC) for an IP address. Returns carrier data only for mobile network IPs; non-mobile IPs return null fields. | | `IPDATA_CO_FIELD_CITY` | Get City from IP | Tool to return only city for an IP. Use when only the city name is required. | | `IPDATA_CO_FIELD_CONTINENT_CODE` | IPData: Continent Code | Retrieve the continent code for a given IP address. Returns a two-letter code (AF, AN, AS, EU, NA, OC, SA) indicating which continent the IP is geographically located in. Use this when you only need the continent information without full IP geolocation details. | | `IPDATA_CO_FIELD_CONTINENT_NAME` | Get Continent Name from IP | Tool to return only continent name for an IP. Use when only the continent name is required. | | `IPDATA_CO_FIELD_COUNT` | IPDATA Field Count | Tool to return only the request count made by your API key in the last 24 hours. Use when monitoring your API usage and you only need the total count. | | `IPDATA_CO_FIELD_COUNTRY_CODE` | IPData: Country Code | Tool to return only country_code for an IP. Use when only the 2-letter country code is required. | | `IPDATA_CO_FIELD_COUNTRY_NAME` | Get Country Name from IP | Get the country name for an IP address using ipdata.co geolocation API. Returns only the country name (e.g., 'United States', 'Germany', 'Japan'). Use this lightweight action when you only need the country name without full IP details. | | `IPDATA_CO_FIELD_CURRENCY` | IPDATA Field Currency | Tool to return only currency object for an IP. Use when currency details are needed. | | `IPDATA_CO_FIELD_EMOJI_FLAG` | Get Emoji Flag from IP | Tool to return only emoji flag for an IP. Use when only the country flag emoji is required. | | `IPDATA_CO_FIELD_EMOJI_UNICODE` | Get Emoji Unicode from IP | Tool to return only emoji_unicode for an IP. Use when only the Unicode country flag emoji is required. | | `IPDATA_CO_FIELD_IP` | IPData: IP | Retrieve the public IP address of the calling client. This action calls the IPData API to determine the caller's external/public IP address. It returns only the IP string with no additional geolocation data. Use this when you need to identify your own public IP address. | | `IPDATA_CO_FIELD_IS_EU` | IPData: Is EU | Tool to return only is_eu for an IP. Use when you need to determine if an IP's country belongs to the EU. | | `IPDATA_CO_FIELD_LANGUAGES` | IPData: Languages | Tool to return only the languages array for an IP. Use when only language details for an IP are required. | | `IPDATA_CO_FIELD_LATITUDE` | IPData: Latitude | Tool to return only the latitude for an IP. Use when only the latitude coordinate is needed. | | `IPDATA_CO_FIELD_LONGITUDE` | Get Longitude from IP | Tool to return only longitude for an IP. Use when only the longitude value is required. | | `IPDATA_CO_FIELD_POSTAL` | IPData: Postal Code | Tool to return only postal code for an IP. Use when only the postal code (ZIP/postcode) is required. | | `IPDATA_CO_FIELD_REGION` | Get Region from IP | Tool to return only region for an IP. Use when only the region name is required. | | `IPDATA_CO_FIELD_REGION_CODE` | IPData: Region Code | Tool to return only region_code for an IP. Use when only the ISO 3166-2 region code is required. | | `IPDATA_CO_FIELD_THREAT` | Get Threat for IP | Retrieve threat intelligence data for a specific IP address or the calling IP. Returns indicators such as Tor exit node status, proxy detection, datacenter/cloud provider identification, known attacker/abuser flags, and blocklist appearances. Use this tool when you need to assess the security risk or reputation of an IP address. | | `IPDATA_CO_FIELD_TIME_ZONE` | IPData: Time Zone | Tool to return only the time_zone object for an IP. Use when only timezone data is required. | | `IPDATA_CO_IP_DATA_BASIC_ASN_FOR_IP` | IPData Basic ASN for IP | Tool to return basic ASN data for a specific IP. Use when you need ASN number, organization, domain, route, and type details. | | `IPDATA_CO_IPDATA_BULK_LOOKUP_V1` | IPData Bulk Lookup V1 | Tool to bulk lookup up to 100 IP addresses via ipdata.co. Use when you have multiple IPs and need geolocation and threat data in one call. | | `IPDATA_CO_IP_DATA_COMPANY_FOR_IP` | Get company data for IP | Tool to retrieve company data for a given IP address. Use when you need the organization name, domain, network prefix, and usage type for an IPv4 or IPv6. | | `IPDATA_CO_IPDATA_EU_LOOKUP_CALLING_IP` | EU IP Lookup (Calling IP) | Lookup geolocation, network, and threat data for the calling client's IP address using the EU-residency endpoint. Use this action when you need IP data processed and stored entirely within the European Union (GDPR compliance). The EU endpoint routes requests only through EU datacenters (Frankfurt, Paris, Ireland). This action automatically detects and returns data for the IP address making the API request. No IP address parameter is needed. | | `IPDATA_CO_IP_DATA_LOOKUP_IP_V1` | IPData Lookup IP V1 | Tool to lookup comprehensive IP information (geolocation, network, company, and threat data) in one call. Use when you need all IP insights together. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ipdata co MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ipdata co. It provides structured and secure access so your agent can perform Ipdata co operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. 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 ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies 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 ```bash pip install composio pydantic-ai python-dotenv ``` ### 3. Set up environment variables 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 ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key ``` ### 4. Import dependencies 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 ```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() ``` ### 5. Create a Tool Router Session 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 ```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") ``` ### 6. Initialize the Pydantic AI Agent 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 ```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." ), ) ``` ### 7. Build the chat interface 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 ```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() ``` ### 8. Run the application What's happening: - The asyncio loop launches the agent and keeps it running until you exit ```python if __name__ == "__main__": asyncio.run(main()) ``` ## Complete Code ```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](https://composio.dev/toolkits/ipdata_co/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ipdata_co/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ipdata_co/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ipdata_co/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ipdata_co/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ipdata_co/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ipdata_co/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ipdata_co/framework/cli) - [Google ADK](https://composio.dev/toolkits/ipdata_co/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ipdata_co/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ipdata_co/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ipdata_co/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ipdata_co/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ipdata_co/framework/crew-ai) ## Related Toolkits - [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management. - [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters. - [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations. - [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions. - [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows. - [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations. - [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements. - [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints. - [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots. - [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches. - [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand. - [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance. - [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows. - [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses. - [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research. - [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction. - [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation. - [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation. ## Frequently Asked Questions ### 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)