How to integrate Ipdata co MCP with LlamaIndex

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

Introduction

This guide walks you through connecting Ipdata co to LlamaIndex 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 LlamaIndex 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:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Ipdata co
  • Connect LlamaIndex to the Ipdata co MCP server
  • Build a Ipdata co-powered agent using LlamaIndex
  • Interact with Ipdata co through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built 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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Ipdata co account and project
  • Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Ipdata co

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Ipdata co access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called ipdata co_llamaindex_agent.py and import the required modules:

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_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")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["ipdata_co"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Ipdata co actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Ipdata co actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, ipdata co)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Ipdata co tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Ipdata co database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Ipdata co

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Ipdata co, then start asking questions.

Complete Code

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

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
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")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["ipdata_co"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Ipdata co actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Ipdata co actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected Ipdata co to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Ipdata co tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

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

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 LlamaIndex?

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