How to integrate AimTell MCP with LangChain

This guide walks you through connecting AimTell to LangChain using the Composio tool router. By the end, you'll have a working AimTell agent that can list aimtell websites by subscriber count, create segment for cart abandoners, summarize campaign delivery analytics this week through natural language commands. This guide will help you understand how to give your LangChain agent real control over a AimTell account through Composio's AimTell MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

AimTell logoAimTell
Api Key

AimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics. Use it to send targeted browser notifications and measure engagement across your web push campaigns.

15 Tools

Introduction

This guide walks you through connecting AimTell to LangChain using the Composio tool router. By the end, you'll have a working AimTell agent that can list aimtell websites by subscriber count, create segment for cart abandoners, summarize campaign delivery analytics this week through natural language commands.

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

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

Also integrate AimTell with

TL;DR

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

The AimTell MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your AimTell account. It provides structured and secure access to your websites, subscribers, campaigns, segments, notifications, and delivery analytics, so your agent can manage audiences, prepare campaigns, send push notifications, review results, and track delivery activity on your behalf.

  • Website and subscriber insights: Have your agent list your AimTell websites, browse subscribers, review their attributes and notification history, and filter audiences by segment.
  • Audience segment management: Let the agent create, update, list, or delete audience segments used to organize subscribers and target campaigns.
  • Campaign draft management: Direct your agent to create and revise manual campaign drafts, review campaigns across supported campaign types, or delete drafts you no longer need.
  • Targeted push notifications: Instruct your agent to send a one-off push notification to selected subscribers, a segment, an alias, or your website's full reachable audience.
  • Delivery and campaign reporting: Have your agent track daily metrics, review campaign sends, deliveries, bounces, clicks, conversions, and revenue where available, or inspect recent notification logs.

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

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

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "aimtell-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 AimTell MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available AimTell 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 AimTell 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 AimTell 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: ['aimtell']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "aimtell-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 AimTell 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 AimTell 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 AimTell action and event your agent gets out of the box.

Create Manual Campaign

Create a manual push campaign as a draft only; this tool never schedules or sends it.

Create Segment

Create a named audience segment for a website from an AimTell segment definition.

Delete Manual Campaign

Permanently delete one manual campaign by ID.

Delete Segment

Permanently delete one audience segment by ID.

Get Analytics Over Time

Return a daily AimTell metric over a date range for all websites or one website.

Get Campaign Results

Return daily send, delivery, bounce, click, conversion, and available revenue results for a manual, event-triggered, RSS, or welcome campaign.

List Campaigns

Return one page of manual, event-triggered, RSS, or API push campaigns for an AimTell website.

List Notification Logs

Return one page from AimTell's sampled notification log for the last seven days, optionally filtered to one subscriber.

List Segments

Return all audience segments for an AimTell website, including the IDs and definitions used for subscriber filtering and campaign targeting.

List Subscribers

Return one page of subscribers for an AimTell website, optionally filtered by segment or subscriber ID and optionally including attributes or notification history.

List Websites

Return one page of websites available to the connected AimTell account, including site IDs needed by other tools.

Send Push Notification

Immediately send a one-off push notification to exactly one explicitly selected audience: subscriber IDs, one segment, one alias, or the website's full reachable audience.

Set Subscriber Attributes

Set custom attributes on one subscriber identified by subscriber UID, user alias, or email alias; supplied aliases may also be associated with the subscriber.

Update Manual Campaign

Update the content or targeting of an unscheduled, unsent, non-A/B manual campaign draft without scheduling or sending it.

Update Segment

Change the name or audience definition of an existing AimTell segment.

FAQ

Frequently asked questions

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

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

Start with AimTell.It takes 30 seconds.

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

Start building