# How to integrate Geoapify MCP with LangChain

```json
{
  "title": "How to integrate Geoapify MCP with LangChain",
  "toolkit": "Geoapify",
  "toolkit_slug": "geoapify",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/geoapify/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/geoapify/framework/langchain.md",
  "updated_at": "2026-05-12T10:12:46.064Z"
}
```

## Introduction

This guide walks you through connecting Geoapify to LangChain using the Composio tool router. By the end, you'll have a working Geoapify agent that can find latitude and longitude for an address, suggest address completions as i type, show reachable area within 10 minutes driving through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Geoapify account through Composio's Geoapify MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Geoapify with

- [OpenAI Agents SDK](https://composio.dev/toolkits/geoapify/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/geoapify/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/geoapify/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/geoapify/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/geoapify/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/geoapify/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/geoapify/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/geoapify/framework/cli)
- [Google ADK](https://composio.dev/toolkits/geoapify/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/geoapify/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/geoapify/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/geoapify/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/geoapify/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Geoapify project to Composio
- Create a Tool Router MCP session for Geoapify
- Initialize an MCP client and retrieve Geoapify tools
- Build a LangChain agent that can interact with Geoapify
- 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 Geoapify MCP server, and what's possible with it?

The Geoapify MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Geoapify account. It provides structured and secure access to powerful location-based services, so your agent can perform actions like geocoding addresses, generating routes, fetching map tiles, and analyzing geographic data on your behalf.
- Address autocomplete and geocoding: Instantly convert partial or full addresses into geographic coordinates, or fetch smart suggestions to speed up location entry.
- Routing and reachability analysis: Generate routes, calculate reachable areas (isochrones/isodistances), and let your agent determine how far you can travel from a point within a set time or distance.
- IP-based geolocation: Look up the approximate location of any IP address to enrich user data, personalize experiences, or detect regions automatically.
- Map visualization and customization: Fetch custom-styled map tiles and create personalized marker icons for fully tailored map displays in your applications or reports.
- Boundary and geometry operations: Retrieve administrative boundaries for any place or coordinate, and perform advanced geometric operations like combining or intersecting polygons to analyze spatial relationships.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GEOAPIFY_ADDRESS_AUTOCOMPLETE` | Address Autocomplete | Tool to fetch address suggestions based on partial input. Use when you need to get predictive suggestions from incomplete address text. |
| `GEOAPIFY_BATCH_REQUESTS` | Batch Requests | Create or retrieve asynchronous batch processing jobs for geocoding, reverse geocoding, routing, or isoline APIs. Use cases: - Batch geocode up to 1000 addresses at once (forward geocoding) - Batch reverse geocode multiple coordinates - Process multiple routing or isoline requests in one batch Workflow: 1. Create a job by providing 'api' and 'inputs' (returns job ID and status 'pending') 2. Poll the job by providing 'id' until status changes from 'pending' to complete (results available) |
| `GEOAPIFY_BOUNDARIES` | Get Boundaries Containing Location | Retrieve all administrative boundaries that contain a given location. Returns hierarchical boundaries (suburb, city, county, state, country) as GeoJSON features. Use this to find what administrative areas a coordinate belongs to, get boundary polygons for mapping, or identify postal codes and political districts for a location. |
| `GEOAPIFY_CREATE_BATCH_FORWARD_GEOCODE_JOB` | Create Batch Forward Geocode Job | Tool to create a batch forward geocoding job for up to 1000 addresses. Use when you need to geocode multiple addresses asynchronously. Returns a job ID for retrieving results once processing is complete. |
| `GEOAPIFY_CREATE_BATCH_REVERSE_GEOCODE_JOB` | Create Batch Reverse Geocode Job | Tool to create a batch reverse geocoding job that converts multiple lat/lon coordinates into addresses asynchronously. Use when you need to reverse geocode multiple coordinates (up to 1000) in one request. Returns a job ID for retrieving results. |
| `GEOAPIFY_FORWARD_GEOCODING` | Forward Geocoding | Tool to convert an address into geographic coordinates. Use when you need latitude and longitude from an address. |
| `GEOAPIFY_GEOMETRY` | Geometry Operation | Tool to perform geometric operations on stored polygon geometries. Use when combining or intersecting multiple stored geometries. |
| `GEOAPIFY_GET_BATCH_FORWARD_GEOCODE_RESULTS` | Get Batch Forward Geocode Results | Tool to retrieve batch forward geocoding job results using the job ID. Use when you need to fetch geocoded addresses from a previously submitted batch job. Results available in JSON or CSV format. Job must be complete (status 200) to get results. |
| `GEOAPIFY_GET_BATCH_REVERSE_GEOCODE_RESULTS` | Get Batch Reverse Geocode Results | Tool to retrieve batch reverse geocoding job results. Use when you have a batch job ID from creating a batch reverse geocoding job and want to fetch the completed results. |
| `GEOAPIFY_GET_BOUNDARIES_CONSISTS_OF` | Get Child Boundaries (Consists Of) | Get boundaries that a specified location consists of. Returns child administrative divisions (states for country, districts for city). Useful for drilling down into sub-regions. |
| `GEOAPIFY_GET_MAP_STYLE` | Get Map Style JSON | Tool to retrieve vector map style JSON for MapLibre GL and Mapbox GL. Returns a Mapbox-compatible style specification for rendering vector tiles. |
| `GEOAPIFY_GET_STATIC_MAP` | Generate Static Map Image | Tool to generate static map images with customizable style, size, center, zoom, markers, and geometries. Use when you need a map image for display or printing. |
| `GEOAPIFY_IP_GEOLOCATION` | IP Geolocation | Lookup geographic location information for an IP address. Returns city-level location data including country, region, city, coordinates, and additional metadata like currency and language. If no IP is provided, returns location for the caller's IP address. |
| `GEOAPIFY_ISOLINE` | Generate isoline (isochrone/isodistance) | Tool to generate isochrone or isodistance isolines. Use when visualizing reachable areas from a point; use `id` to poll ongoing calculations. |
| `GEOAPIFY_LIST_POSTCODES` | List Postcodes | Tool to list postcodes within a specified area or boundary. Use when you need to retrieve multiple postcodes in a geographic region using filters like circle, rectangle, or place ID. |
| `GEOAPIFY_MAP_MATCHING` | Map Matching | Snap GPS traces to the road network for accurate route reconstruction. Use this tool to: - Correct GPS drift and inaccuracies in recorded tracks - Align vehicle/cycling/walking traces to actual roads - Get road names and properties along the matched route - Calculate accurate distance and travel time from GPS data |
| `GEOAPIFY_MAP_TILES` | Fetch Geoapify Map Tiles | Tool to fetch raster map tiles or style JSON from Geoapify. Use when rendering custom maps with specific styles. |
| `GEOAPIFY_MARKER_ICON` | Create Marker Icon | Generate custom map marker icons as PNG images. Creates customizable marker icons for use in mapping applications (Leaflet, MapLibre GL, Google Maps, etc.). Supports multiple styles (material, circle, plain), custom colors, icons from Material Design and Font Awesome libraries, or custom text/numbers. Example use cases: - Create a red location pin with a star icon - Generate numbered markers (1, 2, 3...) for route waypoints - Create custom-colored markers matching your brand |
| `GEOAPIFY_PLACE_DETAILS` | Place Details | Tool to retrieve detailed information about a specific place. Use when you have a place ID or coordinates and need comprehensive metadata. |
| `GEOAPIFY_PLACES` | Places Search | Search for points of interest (POIs) like restaurants, hotels, attractions, hospitals, etc. within a geographic area. Use this tool when you need to find places by category near a location. You must provide either a 'filter' (to search within a bounded area) or 'bias' (to rank results by proximity to a point). Common use cases: - Find restaurants near a location: categories=['catering.restaurant'], bias='proximity:lon,lat' - Search for hotels in a city area: categories=['accommodation.hotel'], filter='circle:lon,lat,5000' - Find wheelchair-accessible attractions: categories=['tourism.attraction'], conditions=['wheelchair'] |
| `GEOAPIFY_POSTCODE` | Postcode Search | Tool to retrieve postcode information for a location. Use when you need to fetch postcode details based on a given postcode or geographic coordinates. |
| `GEOAPIFY_REVERSE_GEOCODING` | Reverse Geocoding | Tool to reverse geocode coordinates into a structured address. Use when converting lat/lon to human-readable addresses. |
| `GEOAPIFY_ROUTE_MATRIX` | Route Matrix | Tool to compute travel time and distance matrices. Use when you need durations and distances between multiple origin and destination pairs. |
| `GEOAPIFY_ROUTE_PLANNER` | Route Planner | Optimize multi-agent routes for deliveries, pickups, and service jobs. Solves Vehicle Routing Problems (VRP) including: Travelling Salesman (TSP), Capacitated VRP, VRP with Time Windows, and Pickup-Delivery problems. Required: Either 'jobs' (one-way tasks) or 'shipments' (pickup-delivery pairs). Coordinates: Use [longitude, latitude] format (not lat/lon). |
| `GEOAPIFY_ROUTING` | Routing | Tool to calculate routes between multiple waypoints. Use when you need both distance, time, and turn-by-turn directions for two or more coordinates. |

## Supported Triggers

None listed.

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

The Geoapify MCP server is an implementation of the Model Context Protocol that connects your AI agent to Geoapify. It provides structured and secure access so your agent can perform Geoapify 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

No description provided.

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

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

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

### 3. Set up environment variables

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

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
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();
```

### 5. Initialize Composio client

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 Geoapify tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
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()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Geoapify 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 Geoapify tools as needed
```python
# Create Tool Router session for Geoapify
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['geoapify']
)

url = session.mcp.url
```

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

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "geoapify-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "geoapify-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 });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Geoapify related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Geoapify 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);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

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

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['geoapify']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "geoapify-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Geoapify related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
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: ['geoapify']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "geoapify-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 Geoapify 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 Geoapify 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.

## How to build Geoapify MCP Agent with another framework

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

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

### Can I use Tool Router MCP with LangChain?

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 Geoapify tools.

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

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

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