How to integrate Discord MCP with LangChain

This guide walks you through connecting Discord to LangChain using the Composio tool router. By the end, you'll have a working Discord agent that can list all discord servers i belong to, show your connected accounts on discord, fetch your discord profile information through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Discord account through Composio's Discord MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Discord logoDiscord
Oauth2

Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.

27 Tools1 Triggers

Introduction

This guide walks you through connecting Discord to LangChain using the Composio tool router. By the end, you'll have a working Discord agent that can list all discord servers i belong to, show your connected accounts on discord, fetch your discord profile information through natural language commands.

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

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

Also integrate Discord with

TL;DR

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

The Discord MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Discord account. It provides structured and secure access to your Discord profile, connected accounts, servers, and invites, so your agent can fetch user details, list your servers (guilds), retrieve invite info, and manage your Discord presence on your behalf.

  • Retrieve and manage user profile information: Your agent can fetch your Discord profile details, including email and connected third-party accounts, to help keep your data organized and up-to-date.
  • Server (guild) discovery and membership checks: Effortlessly list all servers you belong to and verify your membership status in any server.
  • Access invite details and server info: Instantly get information about specific Discord invite codes, including the destination server or channel details.
  • Guild member insights: Allow your agent to retrieve your own guild member information across servers, including permissions and roles.
  • OAuth2 application and authorization review: Let your agent fetch your app’s OAuth2 authorization details, so you always know what permissions are granted and when tokens expire.

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

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

Configure the agent with the MCP URL

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

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "discord-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 Discord 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 Discord 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 & TRIGGERS

Supported Tools and Triggers

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

Consume Entitlement

Marks a one-time purchase consumable entitlement as consumed for a given application.

Delete Test Entitlement

Deletes a currently active test entitlement for a given application.

Delete User Application Role Connection

Deletes the current user's application role connection for the specified application.

Edit Application Command Permissions

Edits the permissions for a specific application command in a guild.

Get Application Command Permissions

Retrieves the permissions for a specific application command in a guild.

Get Batch Application Command Permissions

Retrieves permissions for all commands of an application in a guild.

Get Current User Application Entitlements

Tool to retrieve entitlements for the current user for a given application.

Get Gateway

Tool to retrieve a valid WebSocket (wss) URL for establishing a Gateway connection to Discord.

Get Guild Template

Tool to retrieve information about a Discord guild template using its unique template code.

Get Guild Widget

Tool to retrieve the guild widget in JSON format.

Get Guild Widget PNG

Tool to retrieve a PNG image widget for a Discord guild.

Get my guild member

Retrieves the guild member object for the currently authenticated user within a specified guild, including roles, nickname, join date, and permissions.

Get my OAuth2 authorization

Retrieves current OAuth2 authorization details for the application, including app info, scopes, token expiration, and user data (contingent on scopes like 'identify').

Get My User

Fetches comprehensive profile information for the currently authenticated Discord user, including email if the 'email' scope is granted.

Get OpenID Connect userinfo

Retrieve OpenID Connect compliant user information for the authenticated user.

Get Public Keys

Tool to retrieve Discord OAuth2 public keys.

Get SKU Subscription

Retrieves a specific subscription by ID for a given SKU.

Get User

Retrieve information about a Discord user.

Get User Application Role Connection

Retrieves the application role connection for the currently authenticated user for a specified application.

Resolve Invite

Tool to resolve and retrieve information about a Discord invite code.

Leave Guild

Leaves a Discord guild (server) on behalf of the currently authenticated user.

List My Connections

Retrieves a list of the authenticated user's connected third-party accounts on Discord.

List My Guilds

Lists the current user's guilds, returning partial data for each; primarily used for displaying server lists or verifying memberships.

List SKU Subscriptions

Lists all subscriptions for a given SKU.

List Sticker Packs

Tool to retrieve all available Discord Nitro sticker packs.

Modify Current User

Modifies the currently authenticated Discord user's profile.

Update User Application Role Connection

Updates the application role connection for the currently authenticated user for a specified application.

FAQ

Frequently asked questions

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

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

Start with Discord.It takes 30 seconds.

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

Start building