# How to integrate Whoisfreaks MCP with LlamaIndex

```json
{
  "title": "How to integrate Whoisfreaks MCP with LlamaIndex",
  "toolkit": "Whoisfreaks",
  "toolkit_slug": "whoisfreaks",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/whoisfreaks/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/whoisfreaks/framework/llama-index.md",
  "updated_at": "2026-03-29T06:55:17.657Z"
}
```

## Introduction

This guide walks you through connecting Whoisfreaks to LlamaIndex using the Composio tool router. By the end, you'll have a working Whoisfreaks agent that can get whois info for google.com, check domain registration status for mysite.io, list recent ownership changes for example.org through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Whoisfreaks account through Composio's Whoisfreaks MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Whoisfreaks with

- [OpenAI Agents SDK](https://composio.dev/toolkits/whoisfreaks/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/whoisfreaks/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/whoisfreaks/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/whoisfreaks/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/whoisfreaks/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/whoisfreaks/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/whoisfreaks/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/whoisfreaks/framework/cli)
- [Google ADK](https://composio.dev/toolkits/whoisfreaks/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/whoisfreaks/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/whoisfreaks/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/whoisfreaks/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/whoisfreaks/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 Whoisfreaks
- Connect LlamaIndex to the Whoisfreaks MCP server
- Build a Whoisfreaks-powered agent using LlamaIndex
- Interact with Whoisfreaks 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 Whoisfreaks MCP server, and what's possible with it?

The Whoisfreaks MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Whoisfreaks account. It provides structured and secure access so your agent can perform Whoisfreaks operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `WHOISFREAKS_ASN_WHOIS_LOOKUP` | ASN WHOIS Lookup | Tool to retrieve comprehensive ASN WHOIS information including ownership, network infrastructure, and IP address ranges. Use when you need to identify ASN ownership, organization details, or associated IP blocks for network administration or security analysis. |
| `WHOISFREAKS_BULK_DNS_LOOKUP` | Bulk DNS Lookup | Tool to process multiple domains or IPs simultaneously, returning all DNS records in a single request (max 100). Use when you need to retrieve DNS records for multiple domains at once for efficient batch processing. |
| `WHOISFREAKS_BULK_DOMAIN_AVAILABILITY_CHECK` | Bulk Domain Availability Check | Tool to check availability of multiple domains in one request (max 100 domains). Use when you need to verify if domain names are available for registration. Response time ranges from 16 seconds to 1 minute for 100 domains. |
| `WHOISFREAKS_BULK_WHOIS_LOOKUP` | Bulk WHOIS Lookup | Tool to query WHOIS information for up to 100 domains in a single request. Use when you need comprehensive registration details, contact information, name servers, and domain status for multiple domains. Response includes normalized and parsed WHOIS data with 1 credit charged per successful query for each domain. |
| `WHOISFREAKS_DNS_LIVE_LOOKUP` | DNS Live Lookup | Tool to perform real-time DNS record resolution for network diagnostics and configuration verification. Use when you need to retrieve current DNS records for a domain or perform reverse DNS lookup for an IP address. |
| `WHOISFREAKS_CHECK_DOMAIN_AVAILABILITY` | Check Domain Availability | Tool to check if a domain is available for registration with optional suggestions. Use when you need to verify domain availability or get alternative domain suggestions. |
| `WHOISFREAKS_GET_DOMAIN_FILES_STATUS` | Get Domain Files Status | Tool to check availability and update status of domain data files including newly registered, expired, and dropped domains. Use when you need to verify that domain data files are prepared and ready for download before accessing file download endpoints. |
| `WHOISFREAKS_IP_GEOLOCATION_LOOKUP` | IP Geolocation Lookup | Tool to retrieve geographic location information for an IP address including country, city, coordinates, ISP, and security details. Use when you need to identify the physical location of an IP, detect VPN/proxy usage, or gather network intelligence for security or analytics purposes. |
| `WHOISFREAKS_IP_WHOIS_LOOKUP` | IP WHOIS Lookup | Tool to retrieve comprehensive WHOIS information for an IP address including organization, ISP, and network details. Use when you need to identify IP ownership, allocation status, or contact information for network administration or security purposes. |
| `WHOISFREAKS_SECURITY_THREAT_LOOKUP` | Security Threat Lookup | Tool to check if an IP address is associated with malicious activity, security threats, or appears on blocklists. Use when you need to assess IP reputation, detect VPN/proxy/Tor usage, identify bots or spam sources, or evaluate security risk for access control and fraud prevention. |
| `WHOISFREAKS_SSL_CERTIFICATE_LOOKUP` | SSL Certificate Lookup | Tool to fetch live SSL certificate with full secure cert chain, validity dates, and issuer information. Use when you need to retrieve SSL certificate details for a domain, including certificate validation dates, issuer details, public key information, and certificate extensions. |
| `WHOISFREAKS_SUBDOMAIN_LOOKUP` | Subdomain Lookup | Tool to discover all subdomains associated with a domain name. Use when you need to enumerate subdomains for security assessment, asset discovery, or domain reconnaissance. Supports filtering by active/inactive status and date ranges. |
| `WHOISFREAKS_WHOIS_HISTORICAL_LOOKUP` | WHOIS Historical Lookup | Tool to access historical domain records from comprehensive database with up to 100 records per page. Use when you need to retrieve historical WHOIS data for a domain dating back to 1986. Database is updated monthly with one-month data latency. |
| `WHOISFREAKS_WHOIS_LIVE_LOOKUP` | WHOIS Live Lookup | Tool to fetch real-time WHOIS domain registration data directly from authoritative WHOIS servers. Use when you need current domain ownership, registration dates, contact information, or nameserver details. Note that some fields may show 'REDACTED FOR PRIVACY' due to ICANN privacy regulations. |
| `WHOISFREAKS_WHOIS_LIVE_LOOKUP_V2` | WHOIS Live Lookup V2 | Tool to fetch real-time WHOIS domain data using v2.0 endpoint. Use when you need current domain ownership, registration dates, contact information, or nameserver details via the updated v2.0 API. Note that some fields may show 'REDACTED FOR PRIVACY' due to ICANN privacy regulations. |
| `WHOISFREAKS_WHOIS_REVERSE_LOOKUP_BY_COMPANY` | WHOIS Reverse Lookup By Company | Tool to search for domains registered by a specific company or organization using reverse WHOIS lookup. Use when you need to find all domains associated with a particular company name. Performs full-text phrase matching with pagination support. Charges 5 credits per page retrieved. |
| `WHOISFREAKS_WHOIS_REVERSE_LOOKUP_BY_EMAIL` | WHOIS Reverse Lookup by Email | Tool to search for domains registered with a specific email address. Use when you need to find all domains associated with an email in WHOIS records. Supports exact or regex email matching. Returns paginated results with domain registration details. |
| `WHOISFREAKS_WHOIS_REVERSE_LOOKUP_BY_OWNER` | WHOIS Reverse Lookup By Owner | Tool to search for domains registered by a specific owner name using reverse WHOIS lookup. Use when you need to find all domains associated with a particular registrant or owner name. Performs pattern-based full-text search with pagination support. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Whoisfreaks MCP server is an implementation of the Model Context Protocol that connects your AI agent to Whoisfreaks. It provides structured and secure access so your agent can perform Whoisfreaks 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 Whoisfreaks account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Whoisfreaks

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 Whoisfreaks 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, whoisfreaks)
- 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 Whoisfreaks 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=["whoisfreaks"],
    )

    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 Whoisfreaks actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Whoisfreaks 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: ["whoisfreaks"],
    },
  );

  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 Whoisfreaks 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 Whoisfreaks
```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 Whoisfreaks, 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=["whoisfreaks"],
    )

    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 Whoisfreaks actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Whoisfreaks 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: ["whoisfreaks"],
    },
  );

  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 Whoisfreaks 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 Whoisfreaks to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Whoisfreaks 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 Whoisfreaks MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/whoisfreaks/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/whoisfreaks/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/whoisfreaks/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/whoisfreaks/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/whoisfreaks/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/whoisfreaks/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/whoisfreaks/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/whoisfreaks/framework/cli)
- [Google ADK](https://composio.dev/toolkits/whoisfreaks/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/whoisfreaks/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/whoisfreaks/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/whoisfreaks/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/whoisfreaks/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 Whoisfreaks MCP?

With a standalone Whoisfreaks MCP server, the agents and LLMs can only access a fixed set of Whoisfreaks tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Whoisfreaks 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 Whoisfreaks tools.

### Can I manage the permissions and scopes for Whoisfreaks while using Tool Router?

Yes, absolutely. You can configure which Whoisfreaks 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 Whoisfreaks data and credentials are handled as safely as possible.

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