# How to integrate Ipdata co MCP with LlamaIndex

```json
{
  "title": "How to integrate Ipdata co MCP with LlamaIndex",
  "toolkit": "Ipdata co",
  "toolkit_slug": "ipdata_co",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/ipdata_co/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/ipdata_co/framework/llama-index.md",
  "updated_at": "2026-05-12T10:16:18.761Z"
}
```

## 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 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.

## 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)
- [CrewAI](https://composio.dev/toolkits/ipdata_co/framework/crew-ai)

## 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

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

### 1. Getting API Keys for OpenAI, Composio, and Ipdata co

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

```typescript
npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv
```

### 3. Set environment variables

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
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
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()
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
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")
```

```typescript
const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");
```

### 6. Create a Tool Router session and build the agent function

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.
```python
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)
```

```typescript
async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["ipdata_co"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Ipdata co actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
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}")
```

```typescript
async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}
```

### 8. Define the main entry point

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
```python
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!")
```

```typescript
async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Ipdata co, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
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!")
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["ipdata_co"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Ipdata co actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();
```

## 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](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)
- [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.
- [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.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## 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 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)