How to integrate Postmark MCP with LangChain

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.

Postmark logoPostmark
Api Key

Postmark is an email delivery service for sending transactional emails with reliable deliverability. It delivers detailed analytics and fast, secure email delivery for developers.

46 Tools

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.

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

Step by step10 STEPS
1

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
2

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.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters 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/core is the core agent framework
  • dotenv/config loads environment variables
4

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
5

Import dependencies

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

Initialize Composio client

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

Create a Tool Router session

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

const 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
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "postmark-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 });
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
  • getTools() retrieves all available Postmark tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Postmark 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);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept 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 invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

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: ['postmark']
        }
    );

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

Supported Tools

Every Postmark action and event your agent gets out of the box.

Archive Message Stream

Tool to archive a message stream (soft delete).

Check Spam Score

Tool to assess the spam score of a raw email via the SpamCheck API.

Create Inbound Rule

Tool to create a new inbound rule trigger to block email from a specific sender or domain.

Create Message Stream

Tool to create a new message stream.

Create Suppressions

Tool to add email addresses to the suppression list for a message stream.

Create Template

Tool to create a new email template.

Create Webhook

Tool to create a new webhook configuration for Postmark.

Delete Inbound Rule

Tool to delete a specific inbound rule trigger.

Delete Suppressions

Tool to remove email addresses from the suppression list for a message stream.

Delete Template

Tool to delete a template by its ID or alias.

Delete Webhook

Tool to delete a specific webhook.

Edit Server

Tool to update settings for the current Postmark server.

Edit Template

Tool to update an existing Postmark template by its ID.

Edit Webhook

Tool to update an existing webhook’s URL or triggers.

Get Bounce Counts

Tool to get total counts of emails that have been returned as bounced.

Get Bounces

Tool to retrieve a list of bounces for a server with optional filters.

Get Browser Platform Usage

Tool to retrieve browser platform usage statistics for clicked links.

Get Browser Usage

Tool to retrieve browser usage statistics for clicked links.

Get Click Counts

Tool to retrieve total click counts across all links in emails.

Get Clicks By Browser Family

Tool to retrieve click statistics grouped by browser family.

Get Clicks by Location

Tool to get an overview of which part of the email links were clicked from (HTML or Text).

Get Delivery Stats

Tool to retrieve delivery statistics.

Get Email Client Usage

Tool to retrieve statistics on email clients used to open emails.

Get Email Open Counts

Tool to retrieve counts of opened emails.

Get Message Stream

Tool to retrieve details of a specific message stream by its ID.

Get Opens by Platform

Tool to retrieve email open statistics by platform type.

Get Outbound Overview

Tool to retrieve outbound email statistics overview.

Get Sent Counts

Tool to retrieve total count of emails sent out.

Get Server

Tool to retrieve details of the current Postmark server.

Get Spam Complaints

Tool to retrieve counts of spam complaints.

Get Template

Tool to retrieve details of a specific template by its ID.

Get Tracked Email Counts

Tool to retrieve counts of emails with tracking enabled.

Get Webhook

Tool to retrieve details of a specific webhook by its ID.

List Inbound Rules

Tool to list all inbound rules (triggers) configured for blocking senders.

List Message Streams

Tool to list all message streams for a Postmark server with optional type and archive filtering.

List Outbound Message Clicks

Tool to list clicks for outbound messages with filtering options.

List Outbound Message Opens

Tool to retrieve opens for outbound messages with filtering options.

List Suppressions

Tool to retrieve the suppression list for a message stream with optional filtering.

List Templates

Tool to list all templates for a Postmark server.

List Webhooks

Tool to list all webhooks configured for your Postmark account.

Search Inbound Messages

Tool to search inbound messages received with optional filtering.

Search Outbound Messages

Tool to search outbound messages with filtering by recipient, tag, status, and date range.

Send Batch Templated Emails

Tool to send multiple templated emails in a single batch API call.

Unarchive Message Stream

Tool to unarchive a previously archived message stream.

Update Message Stream

Tool to update a message stream configuration in Postmark.

Validate Template

Tool to validate a Postmark template.

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Postmark.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Postmark tool your agent needs.Free to start.

Start building