How to integrate Big data cloud MCP with LangChain

This guide walks you through connecting Big data cloud to LangChain using the Composio tool router. By the end, you'll have a working Big data cloud agent that can check if this ip address is currently roaming, verify if an email address is valid, get country and demographic info for a given ip through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Big data cloud account through Composio's Big data cloud MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Big data cloud logoBig data cloud
Api Key

BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.

17 Tools

Introduction

This guide walks you through connecting Big data cloud to LangChain using the Composio tool router. By the end, you'll have a working Big data cloud agent that can check if this ip address is currently roaming, verify if an email address is valid, get country and demographic info for a given ip through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Big data cloud account through Composio's Big data cloud MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Big data cloud with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Big data cloud project to Composio
  • Create a Tool Router MCP session for Big data cloud
  • Initialize an MCP client and retrieve Big data cloud tools
  • Build a LangChain agent that can interact with Big data cloud
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Big data cloud MCP server, and what's possible with it?

The Big data cloud MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Big data cloud account. It provides structured and secure access to advanced geolocation, reverse geocoding, ASN analysis, and data validation APIs, so your agent can perform actions like looking up IP details, verifying emails, assessing network risk, and analyzing BGP routing on your behalf.

  • IP geolocation and country insights: Let your agent instantly geolocate any IP address, retrieve country-level demographics, and pull rich metadata about locations worldwide.
  • Reverse geocoding with timezone detection: Have your agent translate GPS coordinates into precise locality information along with accurate timezone data—all in one go.
  • Email address verification and data hygiene: Ensure your agent can validate email addresses for proper syntax, domain legitimacy, and disposability to help maintain clean and reliable datasets.
  • ASN and BGP analytics: Allow your agent to analyze internet routing by fetching ranked lists of autonomous systems, upstream and downstream provider details, and active BGP prefixes for a given ASN.
  • Cybersecurity hazard assessment: Empower your agent to fetch and interpret hazard reports for IP addresses, identifying threats like VPN/proxy usage, blacklist status, and hosting risks.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK 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

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Big data cloud functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Big data cloud tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['big_data_cloud']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Big data cloud 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
  • This approach allows the agent to dynamically load and use Big data cloud tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "big_data_cloud-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Big data cloud MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Big data cloud tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Big data cloud related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Big data cloud and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['big_data_cloud']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "big_data_cloud-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Big data cloud related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Big data cloud through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Big data cloud action and event your agent gets out of the box.

Am I Roaming API

Tool to determine if the user is roaming based on their IP address and GPS coordinates.

ASN Extended Receiving From Info API

Tool to return upstream providers (receivingFrom) for a given ASN.

ASN Extended Transit To Info API

Tool to return downstream customers (transitTo) for a given ASN.

ASN Rank List API

Retrieves a ranked list of Autonomous Systems (ASNs) sorted by IPv4 address announcement volumes.

BGP Active Prefixes API

Tool to retrieve IPv4 or IPv6 prefixes currently announced on BGP.

Country by IP Address API

Tool to geolocate an IP address and retrieve country details and demographics.

Country Info API

Tool to fetch detailed country information by ISO code.

Email Address Verification API

Tool to verify email addresses for syntax, domain validity, and disposability.

Hazard Report API

Tool to fetch a cybersecurity hazard report for a specified IP address.

Networks by CIDR

Tool to retrieve BGP-announced networks within a specified CIDR range.

Network by IP Address API

Tool to retrieve registry, ASN, and BGP details for a given IP address’s network.

Phone Number Validation by IP

Tool to validate phone numbers by inferring country from client IP.

Reverse Geocoding With Timezone API

Tool to return reverse geocoding and time zone info for given coordinates.

Time Zone by IP Address API

Tool to retrieve time zone information for a given IP address.

Tor Exit Nodes Geolocated API

Retrieve a paginated list of active TOR exit node IP addresses with geolocation and carrier (ASN) details.

User Agent Parser API

Tool to parse a User-Agent string into device, OS, browser, and bot details.

User Risk API

Tool to return a risk assessment for a user based on IP signals for fraud prevention.

FAQ

Frequently asked questions

With a standalone Big data cloud MCP server, the agents and LLMs can only access a fixed set of Big data cloud tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Big data cloud and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LangChain 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 Big data cloud tools.

Yes, absolutely. You can configure which Big data cloud 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.

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 Big data cloud data and credentials are handled as safely as possible.

Start with Big data cloud.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Big data cloud tool your agent needs.Free to start.

Start building