How to integrate Textit MCP with LangChain

This guide walks you through connecting Textit to LangChain using the Composio tool router. By the end, you'll have a working Textit agent that can create a new campaign for event reminders, list all contact groups for segmentation, retrieve details about a specific campaign through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Textit account through Composio's Textit MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Textit logoTextit
Api Key

Textit is a platform for building scalable, interactive chatbots across multiple channels—no coding required. It helps businesses automate communication, collect data, and manage chat workflows effortlessly.

31 Tools

Introduction

This guide walks you through connecting Textit to LangChain using the Composio tool router. By the end, you'll have a working Textit agent that can create a new campaign for event reminders, list all contact groups for segmentation, retrieve details about a specific campaign through natural language commands.

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

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

Also integrate Textit with

TL;DR

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

The Textit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Textit account. It provides structured and secure access to your chatbots, contacts, campaigns, and messaging flows, so your agent can create campaigns, manage contact groups, organize labels, retrieve broadcasts, and handle messaging operations on your behalf.

  • Automated campaign management: Let your agent create, retrieve, or list messaging campaigns, helping you launch outreach efforts to targeted contact groups without lifting a finger.
  • Contact group creation and segmentation: Easily segment your audience by having your agent create or delete contact groups, keeping your communication organized and relevant.
  • Custom label organization: Enable your agent to create new message labels, allowing for smarter categorization and easier tracking of important conversations or topics.
  • Broadcast and archive retrieval: Effortlessly fetch lists of broadcasts or message archives, so your agent can provide summaries or analyze past messaging performance.
  • Contact management: Direct your agent to delete outdated or unnecessary contacts, ensuring your database stays clean and up-to-date 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 Textit 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 Textit 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: ['textit']
    }
);

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

Configure the agent with the MCP URL

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

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

Create Campaign

Tool to create a new campaign in TextIt.

Create Contact Group

Tool to create a new contact group.

Create Label

Tool to create a new message label.

Delete Contact

Tool to delete an existing contact.

Delete Contact Group

Tool to delete an existing contact group.

Delete Label

Tool to delete a message label by UUID.

Get Campaign

Tool to retrieve details about a specific campaign.

Get Workspace

Tool to retrieve current workspace details including name, country, languages, and timezone.

List Archives

Tool to retrieve a list of message and run archives.

List Broadcasts

Tool to list broadcasts.

List Campaign Events 2

Tool to retrieve campaign events with optional filtering.

List Campaigns

Tool to list campaigns.

List Channels

Tool to list channels.

List Classifiers

Tool to list NLU classifiers configured for your organization.

List Contacts

Tool to retrieve a list of contacts.

List custom contact fields

Tool to retrieve a list of custom contact fields.

List Flows

Tool to retrieve a list of flows for your organization.

List Flow Starts

Tool to retrieve a list of manual flow starts.

List Globals

Tool to list global variables.

List Groups

Tool to list contact groups for your organization.

List Labels 2

Tool to retrieve a list of message labels for your organization.

List Messages

Tool to retrieve a list of messages.

List Resthook Events

Tool to retrieve recent resthook events for your organization.

List Resthooks

Tool to list configured resthooks (webhooks).

List Resthook Subscribers

Tool to list webhook subscribers for your organization's resthooks.

List Runs

Tool to retrieve a list of flow runs.

List Tickets

Tool to retrieve support tickets for your organization.

List Topics V2

Tool to list topics in the workspace for categorizing tickets.

List Users

Tool to retrieve a list of user logins in your workspace with their roles and teams.

Send Broadcast

Tool to send a new broadcast message.

Update Contact

Tool to update an existing contact.

FAQ

Frequently asked questions

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

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

Start with Textit.It takes 30 seconds.

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

Start building