How to integrate Smtp2go MCP with LangChain

Framework Integration Gradient
Smtp2go Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting Smtp2go to LangChain using the Composio tool router. By the end, you'll have a working Smtp2go agent that can search for bounced emails this week, add marketing@mydomain.com as allowed sender, list all verified sender domains, remove old ip address from allow list through natural language commands.

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

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

TL;DR

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

The Smtp2go MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Smtp2go account. It provides structured and secure access to your email sending and management infrastructure, so your agent can perform actions like searching email activity, managing allowed senders, updating sender domains, and controlling IP allow lists on your behalf.

  • Comprehensive email activity search: Ask your agent to filter and retrieve email events such as sends, opens, clicks, and bounces by recipient, date, or message ID.
  • Allowed sender management: Have your agent add, update, remove, or view allowed sender email addresses to control who can send emails from your account.
  • Sender domain configuration: Let the agent register new sender domains for SPF/DKIM verification and manage domain-related settings seamlessly.
  • IP allow list control: Direct your agent to add or remove IP addresses or CIDR ranges in your account’s IP allow list, enhancing security for sending sources.
  • Email delivery monitoring: Enable your agent to search and analyze sent emails, helping you monitor delivery, troubleshoot issues, and ensure reliable communication.

Supported Tools & Triggers

Tools
Search Email ActivityTool to search activity events like sends, opens, clicks, and bounces.
Add Allowed SenderTool to add a new allowed sender email address.
Remove Allowed SenderTool to remove a sender email address from the allowed senders list.
Update Allowed SenderTool to update details of an existing allowed sender.
View Allowed SendersTool to view the list of allowed senders configured in your account.
Add Sender DomainTool to add a new sender domain for spf/dkim verification.
Search SMTP2GO EmailsTool to search sent emails.
Add IP Allow ListTool to add an ip address or cidr range to your account’s ip allow list.
Remove IP from Allow ListTool to remove an ip address from your account's ip allow list.
View IP Allow ListTool to view the list of ip addresses in your ip allow list.
View Received SMSTool to retrieve received sms replies for your smtp2go account.
Get Email Bounces StatsTool to retrieve email bounces statistics.
Email Cycle StatisticsTool to retrieve email cycle statistics.
Email History StatisticsTool to retrieve email history statistics.
Email Spam StatisticsTool to retrieve email spam report statistics.
Email Unsubscription StatsTool to retrieve email unsubscribe statistics.
Search SubaccountsTool to search subaccounts.
Subaccounts UsageTool to retrieve usage statistics for subaccounts.
Add to Suppression ListTool to add email addresses or domains to the suppression list.
Remove suppression entryTool to remove an email address or domain from the suppression list.
View Suppression ListTool to view the suppression list.
Edit Email TemplateTool to edit details of an existing email template.
Search Email TemplatesTool to search your collection of email templates by id or name.
View Email TemplateTool to view details of a specific email template.
Add SMTP UserTool to add a new smtp user.
Edit SMTP UserTool to edit details of an existing smtp user.
Remove SMTP UserTool to remove an smtp user from your account.
View SMTP UsersTool to list all smtp users configured on your account.
Add WebhookTool to create a new webhook.
Edit WebhookTool to edit an existing webhook’s settings.
Remove webhookTool to remove a webhook.
View WebhooksTool to view all webhooks configured in your account.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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 Smtp2go 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 Smtp2go tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

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

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

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "smtp2go-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 Smtp2go MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Smtp2go 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 Smtp2go 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 Smtp2go 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=['smtp2go']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "smtp2go-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 Smtp2go 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 Smtp2go 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 Smtp2go MCP Agent with another framework

FAQ

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

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.