How to integrate Missive MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Missive logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Missive to the Claude Agent SDK 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 Claude Agent SDK 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

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Missive
  • Configure an AI agent that can use Missive as a tool
  • Run a live chat session where you can ask the agent to perform Missive operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 & Triggers

Tools
Create Analytics ReportTool to create an analytics report.
Create Missive ContactsTool to create one or more contacts in a Missive contact book.
Create DraftTool to create a new draft in Missive.
Create Missive PostTool to create a post in a Missive conversation.
Create Canned ResponseTool to create one or more canned responses (templates) in Missive.
Create Shared LabelTool to create one or more shared labels at the organization level.
Create Missive TaskTool to create a task in Missive.
Create TeamTool to create a new team in an organization.
Create WebhookTool to create a webhook subscription.
Delete DraftTool to delete a draft from a conversation by draft ID.
Delete PostTool to delete a post from a conversation by post ID.
Delete Saved ResponsesTool to delete one or more saved responses by ID.
Delete WebhookTool to delete a webhook subscription by webhook ID.
Get Analytics ReportTool to fetch a completed analytics report using its ID.
Get Missive ContactTool to fetch a specific contact using the contact ID.
Get Missive ConversationTool to fetch full conversation metadata (assignees/users/labels/team/org) for a specific conversation ID.
List Conversation MessagesTool to list messages belonging to a Missive conversation (newest first).
Get Missive MessageTool to fetch full message details including headers, HTML body, and attachments.
Get Missive ResponseTool to fetch a specific saved response using the response ID.
Get Missive TaskTool to get a single task by ID with full details including assignees, team, and conversation info.
List Missive Contact BooksTool to list contact books the authenticated user has access to.
List Missive Contact GroupsTool to list contact groups or organizations linked to a contact book.
List Missive ContactsTool to list contacts from a contact book.
List Conversation CommentsTool to list comments in a Missive conversation ordered from newest to oldest.
List Conversation DraftsTool to list draft messages in a Missive conversation (newest first).
List Conversation PostsTool to list posts in a Missive conversation ordered by newest first.
List Missive ConversationsTool to list conversations visible to the authenticated user ordered by newest activity first.
List Messages by Message-IDTool to fetch messages matching an email Message-ID header.
List Missive OrganizationsTool to list organizations the authenticated user is part of.
List Missive Saved ResponsesTool to list saved responses (canned responses/templates) for the authenticated user.
List Missive Shared LabelsTool to list shared labels (organization-level labels) available to the authenticated user.
List Missive TasksTool to list tasks accessible to the authenticated user.
List Missive TeamsTool to list all teams.
List Missive UsersTool to list all users.
Merge Missive ConversationsTool to merge multiple conversations into one.
Update Missive ContactTool to update one or more contacts in Missive.
Update Saved ResponseTool to update one or more saved responses in Missive.
Update Shared LabelsTool to update one or more shared labels in Missive.
Update Missive TaskTool to update an existing task's attributes in Missive.
Update Missive TeamTool to update one or more teams in Missive.

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

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Missive account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Missive functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Missive
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["missive"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Missive
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Missive tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Missive
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Missive and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Missive
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["missive"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Missive tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Missive through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Missive MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Missive MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Missive MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Missive MCP with Claude Cowork

Codex logo

Codex

Use Missive MCP with Codex

OpenClaw logo

OpenClaw

Use Missive MCP with OpenClaw

Hermes logo

Hermes

Use Missive MCP with Hermes

CLI logo

CLI

Use Missive MCP with CLI

Google ADK logo

Google ADK

Use Missive MCP with Google ADK

LangChain logo

LangChain

Use Missive MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Missive MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Missive MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Missive MCP with LlamaIndex

CrewAI logo

CrewAI

Use Missive MCP with CrewAI

FAQ

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗