How to integrate Postmark MCP with LangChain

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

30 min · no commitment · see it on your stack

Postmark logo
LangChain logo
divider

Introduction

This guide walks you through connecting Postmark to LangChain using the Composio tool router. By the end, you'll have a working Postmark agent that can send a password reset email to user, get delivery status for last 10 emails, list all bounced emails from today through natural language commands.

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

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

Also integrate Postmark with

TL;DR

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

The Postmark MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Postmark account. It provides structured and secure access to transactional email sending and analytics, so your agent can perform actions like delivering transactional emails, monitoring delivery status, managing templates, and analyzing engagement metrics on your behalf.

  • Automated transactional email delivery: Let your agent send password resets, confirmations, and notification emails with high deliverability and reliability.
  • Template management and customization: Enable your agent to create, update, or select dynamic email templates for consistent, branded communications.
  • Email delivery status monitoring: Ask your agent to track sent messages, check delivery receipts, and identify bounced or failed emails in real time.
  • Engagement and analytics tracking: Have your agent retrieve open and click data, analyze engagement trends, and provide actionable insights from your email campaigns.
  • Suppression list and recipient management: Direct your agent to manage suppression lists, process unsubscribes, and maintain healthy recipient lists automatically.

Supported Tools & Triggers

Tools
Archive Message StreamTool to archive a message stream (soft delete).
Check Spam ScoreTool to assess the spam score of a raw email via the SpamCheck API.
Create Inbound RuleTool to create a new inbound rule trigger to block email from a specific sender or domain.
Create Message StreamTool to create a new message stream.
Create SuppressionsTool to add email addresses to the suppression list for a message stream.
Create TemplateTool to create a new email template.
Create WebhookTool to create a new webhook configuration for Postmark.
Delete Inbound RuleTool to delete a specific inbound rule trigger.
Delete SuppressionsTool to remove email addresses from the suppression list for a message stream.
Delete TemplateTool to delete a template by its ID or alias.
Delete WebhookTool to delete a specific webhook.
Edit ServerTool to update settings for the current Postmark server.
Edit TemplateTool to update an existing Postmark template by its ID.
Edit WebhookTool to update an existing webhook’s URL or triggers.
Get Bounce CountsTool to get total counts of emails that have been returned as bounced.
Get BouncesTool to retrieve a list of bounces for a server with optional filters.
Get Browser Platform UsageTool to retrieve browser platform usage statistics for clicked links.
Get Browser UsageTool to retrieve browser usage statistics for clicked links.
Get Click CountsTool to retrieve total click counts across all links in emails.
Get Clicks By Browser FamilyTool to retrieve click statistics grouped by browser family.
Get Clicks by LocationTool to get an overview of which part of the email links were clicked from (HTML or Text).
Get Delivery StatsTool to retrieve delivery statistics.
Get Email Client UsageTool to retrieve statistics on email clients used to open emails.
Get Email Open CountsTool to retrieve counts of opened emails.
Get Message StreamTool to retrieve details of a specific message stream by its ID.
Get Opens by PlatformTool to retrieve email open statistics by platform type.
Get Outbound OverviewTool to retrieve outbound email statistics overview.
Get Sent CountsTool to retrieve total count of emails sent out.
Get ServerTool to retrieve details of the current Postmark server.
Get Spam ComplaintsTool to retrieve counts of spam complaints.
Get TemplateTool to retrieve details of a specific template by its ID.
Get Tracked Email CountsTool to retrieve counts of emails with tracking enabled.
Get WebhookTool to retrieve details of a specific webhook by its ID.
List Inbound RulesTool to list all inbound rules (triggers) configured for blocking senders.
List Message StreamsTool to list all message streams for a Postmark server with optional type and archive filtering.
List Outbound Message ClicksTool to list clicks for outbound messages with filtering options.
List Outbound Message OpensTool to retrieve opens for outbound messages with filtering options.
List SuppressionsTool to retrieve the suppression list for a message stream with optional filtering.
List TemplatesTool to list all templates for a Postmark server.
List WebhooksTool to list all webhooks configured for your Postmark account.
Search Inbound MessagesTool to search inbound messages received with optional filtering.
Search Outbound MessagesTool to search outbound messages with filtering by recipient, tag, status, and date range.
Send Batch Templated EmailsTool to send multiple templated emails in a single batch API call.
Unarchive Message StreamTool to unarchive a previously archived message stream.
Update Message StreamTool to update a message stream configuration in Postmark.
Validate TemplateTool to validate a Postmark template.

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 this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

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

Install dependencies

pip install composio-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

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

Import dependencies

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()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Postmark functionality through MCP

Initialize Composio client

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")
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 Postmark tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Postmark
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['postmark']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Postmark 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 Postmark tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "postmark-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)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Postmark MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Postmark tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Postmark 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")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with Postmark and LangChain:

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=['postmark']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "postmark-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 Postmark 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())

Conclusion

You've successfully built a LangChain agent that can interact with Postmark 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 Postmark MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Postmark MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Postmark MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Postmark MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Postmark MCP with Claude Cowork

Codex logo

Codex

Use Postmark MCP with Codex

OpenClaw logo

OpenClaw

Use Postmark MCP with OpenClaw

Hermes logo

Hermes

Use Postmark MCP with Hermes

CLI logo

CLI

Use Postmark MCP with CLI

Google ADK logo

Google ADK

Use Postmark MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Postmark MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Postmark MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Postmark MCP with LlamaIndex

CrewAI logo

CrewAI

Use Postmark MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Postmark MCP?

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

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

Yes, absolutely. You can configure which Postmark 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 Postmark 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↗