# How to integrate Missive MCP with LangChain

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

## Introduction

This guide walks you through connecting Missive to LangChain using the Composio tool router. By the end, you'll have a working Missive agent that can list all team members for marketing, create a draft email for client follow-up, send a chat message in project conversation through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Missive account through Composio's Missive MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Missive with

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

## TL;DR

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

The Missive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Missive account. It provides structured and secure access to your team's shared inboxes and chat threads, so your agent can perform actions like drafting emails, sending messages, generating reports, and managing team communication on your behalf.
- Automated message drafting and scheduling: Let your agent create and save email, SMS, WhatsApp, or live chat drafts for later editing or scheduled sending.
- Instant message sending in conversations: Have your agent send new messages directly to any Missive conversation, keeping your team in the loop in real time.
- Team and user management: Effortlessly list all teams and their members, or pull a full directory of users in your Missive organization for easy coordination and task assignment.
- Analytics report generation: Direct your agent to create detailed analytics reports across time ranges and filters, helping your team track productivity and engagement.
- Webhook automation setup: Enable your agent to create or delete webhook subscriptions, so you can automate notifications and integrations with other tools as needed.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `MISSIVE_CREATE_ANALYTICS_REPORT` | Create Analytics Report | Tool to create an analytics report. Use when you need to generate a report over a specific time range with optional filters. Returns a report ID for later retrieval. |
| `MISSIVE_CREATE_CONTACTS` | Create Missive Contacts | Tool to create one or more contacts in a Missive contact book. Use when you need to add new contacts with detailed information including name, email, phone, addresses, and organization memberships. |
| `MISSIVE_CREATE_DRAFT` | Create Draft | Tool to create a new draft in Missive. Use after preparing message details to save a draft (email, SMS, WhatsApp, or Live Chat) for later editing or scheduling. |
| `MISSIVE_CREATE_POST` | Create Missive Post | Tool to create a post in a Missive conversation. Posts can add comments, close conversations, assign users, apply labels, and trigger other actions. Recommended approach for managing conversations from integrations and automations. |
| `MISSIVE_CREATE_RESPONSE` | Create Canned Response | Tool to create one or more canned responses (templates) in Missive. Use when you need to save reusable message templates for the organization or user. |
| `MISSIVE_CREATE_SHARED_LABEL` | Create Shared Label | Tool to create one or more shared labels at the organization level. Use when you need to create new labels that can be shared across the organization. |
| `MISSIVE_CREATE_TASK` | Create Missive Task | Tool to create a task in Missive. Use when you need to create standalone tasks, conversation-linked subtasks, or team tasks. You can find or create parent conversations using message references (like email Message-IDs). |
| `MISSIVE_CREATE_TEAM` | Create Team | Tool to create a new team in an organization. Use when you need to set up a new team with active members and optional observers. The API token must belong to an organization admin. |
| `MISSIVE_CREATE_WEBHOOK` | Create Webhook | Tool to create a webhook subscription. Use after choosing event type and target URL. |
| `MISSIVE_DELETE_DRAFT` | Delete Draft | Tool to delete a draft from a conversation by draft ID. Use after confirming the draft ID; this operation cannot be undone. |
| `MISSIVE_DELETE_POST` | Delete Post | Tool to delete a post from a conversation by post ID. Use when you need to remove a specific post; this operation cannot be undone. |
| `MISSIVE_DELETE_RESPONSES` | Delete Saved Responses | Tool to delete one or more saved responses by ID. For organization responses, the API token must belong to an admin. Use after confirming the response ID(s); this operation cannot be undone. |
| `MISSIVE_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a webhook subscription by webhook ID. Use after confirming the webhook ID; this operation cannot be undone. |
| `MISSIVE_GET_ANALYTICS_REPORT` | Get Analytics Report | Tool to fetch a completed analytics report using its ID. Use when you need to retrieve analytics data after creating a report. Reports typically complete within 2-3 seconds but may take up to 30 seconds. Reports expire 60 seconds after completion and return 404 if incomplete, expired, or non-existent. |
| `MISSIVE_GET_CONTACT` | Get Missive Contact | Tool to fetch a specific contact using the contact ID. Use when you need detailed contact information including names, contact info, and organizational memberships. Returns 404 for deleted contacts. |
| `MISSIVE_GET_CONVERSATION` | Get Missive Conversation | Tool to fetch full conversation metadata (assignees/users/labels/team/org) for a specific conversation ID. Use when you need conversation-level details for assignment, labeling, or workflow purposes. |
| `MISSIVE_GET_CONVERSATION_MESSAGES` | List Conversation Messages | Tool to list messages belonging to a Missive conversation (newest first). Use when you need to retrieve message metadata including participants and attachments references for a specific conversation. |
| `MISSIVE_GET_MESSAGE` | Get Missive Message | Tool to fetch full message details including headers, HTML body, and attachments. Use when you need complete message content with download URLs for attachments. |
| `MISSIVE_GET_RESPONSE` | Get Missive Response | Tool to fetch a specific saved response using the response ID. Use when you need to retrieve the full content and metadata of a saved response template. |
| `MISSIVE_GET_TASK` | Get Missive Task | Tool to get a single task by ID with full details including assignees, team, and conversation info. Use when you need to retrieve complete information about a specific task. |
| `MISSIVE_LIST_CONTACT_BOOKS` | List Missive Contact Books | Tool to list contact books the authenticated user has access to. Use when you need contact book IDs for creating contacts programmatically. |
| `MISSIVE_LIST_CONTACT_GROUPS` | List Missive Contact Groups | Tool to list contact groups or organizations linked to a contact book. Use when you need to retrieve groups for organizing contacts or organizations for linking contacts to businesses. |
| `MISSIVE_LIST_CONTACTS` | List Missive Contacts | Tool to list contacts from a contact book. Use when syncing Missive contacts to another service or finding contacts based on search terms. Supports pagination via offset and filtering by modification date. |
| `MISSIVE_LIST_CONVERSATION_COMMENTS` | List Conversation Comments | Tool to list comments in a Missive conversation ordered from newest to oldest. Use when you need to retrieve comments with author info, attachments, and task data for a specific conversation. |
| `MISSIVE_LIST_CONVERSATION_DRAFTS` | List Conversation Drafts | Tool to list draft messages in a Missive conversation (newest first). Use when you need to retrieve unsent drafts for a specific conversation including author and recipient details. |
| `MISSIVE_LIST_CONVERSATION_POSTS` | List Conversation Posts | Tool to list posts in a Missive conversation ordered by newest first. Use when you need to view automation traces or post history for a specific conversation. Posts are the recommended approach for automations as they leave a visible trace. |
| `MISSIVE_LIST_CONVERSATIONS` | List Missive Conversations | Tool to list conversations visible to the authenticated user ordered by newest activity first. Use when you need to retrieve inbox, all, assigned, closed, or other mailbox conversations. Must filter by at least one of: mailbox flag, shared label, or team parameter. |
| `MISSIVE_LIST_MESSAGES` | List Messages by Message-ID | Tool to fetch messages matching an email Message-ID header. Use when you need to find a specific message by its Message-ID. Most of the time, only one message matches a given Message-ID. |
| `MISSIVE_LIST_ORGANIZATIONS` | List Missive Organizations | Tool to list organizations the authenticated user is part of. Use when you need to retrieve all organizations accessible to the current user. |
| `MISSIVE_LIST_RESPONSES` | List Missive Saved Responses | Tool to list saved responses (canned responses/templates) for the authenticated user. Use when you need to retrieve available response templates for composing messages. |
| `MISSIVE_LIST_SHARED_LABELS` | List Missive Shared Labels | Tool to list shared labels (organization-level labels) available to the authenticated user. Use when you need to retrieve labels for filtering conversations or understanding label structure. |
| `MISSIVE_LIST_TASKS` | List Missive Tasks | Tool to list tasks accessible to the authenticated user. Use when you need to retrieve tasks by state, organization, or team. Tasks can be standalone, conversation-linked, or team tasks. |
| `MISSIVE_LIST_TEAMS` | List Missive Teams | Tool to list all teams. Use when you need to retrieve and enumerate all teams available in Missive. Returns an empty array for accounts with no teams configured; this is a valid response, not an error. |
| `MISSIVE_LIST_USERS` | List Missive Users | Tool to list all users. Use after authentication when you need to retrieve all users in the organization. |
| `MISSIVE_MERGE_CONVERSATIONS` | Merge Missive Conversations | Tool to merge multiple conversations into one. Combines messages, posts, and other content from the source conversation into the target conversation. Use when you need to consolidate related conversations. |
| `MISSIVE_UPDATE_CONTACT` | Update Missive Contact | Tool to update one or more contacts in Missive. Use when you need to modify contact attributes. Only pass fields you want to update. CRITICAL: infos and memberships arrays must include ALL items when passed - omitted entries will be permanently deleted. |
| `MISSIVE_UPDATE_RESPONSE` | Update Saved Response | Tool to update one or more saved responses in Missive. Use when you need to modify existing response templates by changing title, body, subject, or other attributes. Returns the updated responses. |
| `MISSIVE_UPDATE_SHARED_LABELS` | Update Shared Labels | Tool to update one or more shared labels in Missive. Use when you need to modify label names or colors. Returns the updated shared labels. |
| `MISSIVE_UPDATE_TASK` | Update Missive Task | Tool to update an existing task's attributes in Missive. Use when you need to modify a task's description, change its state, update the due date, or reassign it to different users. |
| `MISSIVE_UPDATE_TEAM` | Update Missive Team | Tool to update one or more teams in Missive. Use when you need to modify team attributes like name, color, or initials. The API token must belong to an organization admin. |

## Supported Triggers

None listed.

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

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

url = session.mcp.url
```

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

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

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

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

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

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

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

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity.
- [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease.
- [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace.
- [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms.
- [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates.
- [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices.
- [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.
- [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks.
- [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission.
- [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.
- [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere.

## Frequently Asked Questions

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

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

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

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

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