# How to integrate Callpage MCP with LangChain

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

## Introduction

This guide walks you through connecting Callpage to LangChain using the Composio tool router. By the end, you'll have a working Callpage agent that can list all widgets with enabled status, get sms statistics for widget 12345, create a custom voice message for spanish visitors through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Callpage account through Composio's Callpage MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Callpage with

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

## TL;DR

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

The Callpage MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Callpage account. It provides structured and secure access to your Callpage lead management tools, so your agent can perform actions like retrieving widgets, managing users, monitoring SMS activity, and customizing voice messages on your behalf.
- Retrieve and manage widgets: Quickly list all your Callpage widgets, access detailed widget configurations, and monitor widget status statistics to optimize lead capture.
- View and audit account users: Effortlessly fetch lists of all users and managers, including status summaries, to keep your team structure up to date and compliant.
- Monitor SMS and messaging activity: Access all SMS messages and gather statistics on SMS usage for specific widgets, helping you track engagement and campaign reach.
- Create custom voice messages: Enable your agent to generate personalized voice greetings for widgets, tailoring communication for both managers and visitors with ease.
- API connectivity and health checks: Let your agent verify API connectivity and status, ensuring seamless and reliable integration between Callpage and your workflows.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CALLPAGE_ADD_USERS_TO_WIDGET` | Add Users to Widget | Tool to add users to a widget as managers. Use when you need to create or update manager assignments for a widget. If a user-widget pair already exists, the existing manager will be updated instead of creating a new one. |
| `CALLPAGE_CREATE_SMS_MESSAGE` | Create SMS Message | Tool to create custom SMS messages for specific widget events. Use when you need to set up automated SMS notifications for call events like completed dials, scheduled calls, or missed calls. |
| `CALLPAGE_CREATE_USER` | Create User | Tool to create a new user with specified name, phone number, email and role. Use when you need to add a new admin or manager user to your CallPage account. |
| `CALLPAGE_DELETE_MANAGER` | Delete Manager | Tool to delete a manager from a widget. Use when you need to remove a manager assignment after verifying both user_id and widget_id. |
| `CALLPAGE_DELETE_USER` | Delete User by Id | Tool to delete a user by id. Use when you need to remove an existing user after verifying their ID. |
| `CALLPAGE_GET_ALL_MANAGERS` | Get All Managers | Tool to retrieve a list of managers for a specific widget with pagination. Use when you need to page through all managers assigned to a widget after confirming its ID. |
| `CALLPAGE_GET_ALL_SMS_MESSAGES` | Get All SMS Messages | Tool to retrieve all SMS messages for a widget. Use when you need to fetch both default and custom SMS templates after confirming the widget exists. |
| `CALLPAGE_GET_ALL_USERS` | Get All Users | Tool to retrieve a list of all users with pagination. Use when you need to page through all users in your CallPage account to synchronize or audit user records. |
| `CALLPAGE_GET_ALL_VOICE_MESSAGES` | Get All Voice Messages | Tool to retrieve all voice messages for a widget. Returns custom voice messages if configured, otherwise returns default messages. Use when you need to view or audit voice message settings. |
| `CALLPAGE_GET_ALL_WIDGETS` | Get All Widgets | Tool to retrieve a list of widgets with pagination. Use when you need to page through all widgets after API authentication. |
| `CALLPAGE_GET_API_ROOT` | Get API Root | Tool to get the root API greeting. Use to verify connectivity and retrieve the initial API greeting after setting the API key. |
| `CALLPAGE_GET_CALLS_HISTORY` | Get Calls History | Tool to retrieve calls history with filtering and pagination. By default returns all calls for all users' widgets. Use when you need to query historical call data with optional filters for date range, status, widgets, users, tags, or phone numbers. |
| `CALLPAGE_GET_MANAGER` | Get Manager | Tool to retrieve a specific manager by user_id and widget_id. Use when you need detailed information about a manager's configuration, availability, and assigned departments. |
| `CALLPAGE_GET_MANAGER_STATUS_STATISTICS` | Get Manager Status Statistics | Tool to retrieve statistical data about manager statuses. Use when you need summary counts of enabled and disabled managers for a specific widget. |
| `CALLPAGE_GET_WIDGET` | Get Widget | Tool to retrieve details of a specific widget by id. Use when you have a widget id and need its complete configuration. |
| `CALLPAGE_POST_CREATE_MANAGER` | Create Manager | Tool to create a new manager for a widget. Use when you need to assign a user as a manager to handle calls for a specific widget. |
| `CALLPAGE_POST_CREATE_VOICE_MESSAGE` | Create Voice Message | Tool to create a custom voice message for a widget. Use when you need to customize greeting messages for manager or visitor after setting widget locale. |
| `CALLPAGE_POST_CREATE_WIDGET` | Create Widget | Tool to create a new widget. Use when you need to install a widget on your site and retrieve its ID. |
| `CALLPAGE_POST_DELETE_WIDGET` | Delete Widget by Id | Tool to delete a widget by id. Use when you need to remove an existing widget after verifying its ID. Example: Delete widget with id 3409. |
| `CALLPAGE_POST_RESET_SMS` | Reset SMS | Tool to reset SMS messages to default for a widget. Use when you need to restore default SMS templates after customization tests. |
| `CALLPAGE_POST_RESET_VOICE_MESSAGE` | Reset Voice Messages | Tool to reset voice messages to default for a widget. Use when you need to clear custom messages and revert to system defaults. Example: Reset all voice messages for widget with id 123. |
| `CALLPAGE_POST_UPDATE_MANAGER` | Update Manager | Tool to update an existing manager. Use when you need to modify a manager's availability or business hours after retrieving their record. |
| `CALLPAGE_POST_UPDATE_SMS` | Update SMS | Tool to update a custom SMS message for a widget. Use when you need to modify custom SMS templates. Note: it's impossible to update default SMS - if you haven't created custom SMS yet, use the create endpoint first. |
| `CALLPAGE_POST_UPDATE_USER` | Update User | Tool to update an existing user by ID. Use when you need to modify a user's details, phone number, role, or enabled status. This operation can override parent user depending on who makes the request. |
| `CALLPAGE_POST_UPDATE_WIDGET` | Update Widget | Tool to update an existing widget. Use when you need to change widget URL, description, settings, language, or enabled state. |
| `CALLPAGE_POST_WIDGET_CALL_OR_SCHEDULE` | Widget Call or Schedule | Tool to initiate or schedule a call via widget. Use when you need to call immediately or schedule at the first available timeslot through a widget. |

## Supported Triggers

None listed.

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

The Callpage MCP server is an implementation of the Model Context Protocol that connects your AI agent to Callpage. It provides structured and secure access so your agent can perform Callpage 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 Callpage 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 Callpage 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 Callpage tools as needed
```python
# Create Tool Router session for Callpage
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['callpage']
)

url = session.mcp.url
```

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

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

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

No description provided.
```python
client = MultiServerMCPClient({
    "callpage-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({
    "callpage-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 Callpage 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 Callpage 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=['callpage']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "callpage-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 Callpage 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: ['callpage']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "callpage-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 Callpage 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 Callpage 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 Callpage MCP Agent with another framework

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

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality.
- [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.
- [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Callpage MCP?

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

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

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

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