How to integrate Postmark MCP with LlamaIndex

This guide walks you through connecting Postmark to LlamaIndex 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 LlamaIndex 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 LlamaIndex 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 LlamaIndex 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:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Postmark
  • Connect LlamaIndex to the Postmark MCP server
  • Build a Postmark-powered agent using LlamaIndex
  • Interact with Postmark through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Postmark account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Postmark

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Postmark access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called postmark_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["postmark"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Postmark actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, postmark)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Postmark tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Postmark
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Postmark tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Postmark
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Postmark, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["postmark"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Postmark actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Postmark to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Postmark tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
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. LlamaIndex 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