How to integrate Listennotes MCP with LangChain

This guide walks you through connecting Listennotes to LangChain using the Composio tool router. By the end, you'll have a working Listennotes agent that can find top tech podcasts from last week, get audience stats for this podcast, list curated playlists about entrepreneurship through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Listennotes account through Composio's Listennotes MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Listennotes logoListennotes
Api Key

Listennotes is a powerful podcast search engine with a massive global database. Discover, search, and curate podcasts from around the world in seconds.

26 Tools

Introduction

This guide walks you through connecting Listennotes to LangChain using the Composio tool router. By the end, you'll have a working Listennotes agent that can find top tech podcasts from last week, get audience stats for this podcast, list curated playlists about entrepreneurship through natural language commands.

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

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

Also integrate Listennotes with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

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

The Listennotes MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Listennotes account. It provides structured and secure access to the Listennotes podcast search platform, so your agent can discover, analyze, and organize podcasts, retrieve episode details, and explore curated recommendations on your behalf.

  • Powerful podcast discovery and search: Let your agent fetch top-rated or genre-specific podcasts, explore curated lists, or search for the best shows to match your interests.
  • In-depth episode and podcast metadata retrieval: Retrieve detailed information about specific episodes or podcasts, including descriptions, publication dates, and audience metrics, to support research or content curation.
  • Bulk data operations for podcasts and episodes: Fetch metadata for multiple podcasts or episodes in a single request, making it easy to keep libraries or dashboards up to date with the latest content.
  • Playlist and curated collection management: Access and organize playlists or curated collections, helping users browse, recommend, or share themed groups of podcasts.
  • Genre exploration and content organization: Retrieve comprehensive genre lists to power advanced filtering, personalized recommendations, or dynamic content categorization.

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 Listennotes 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 Listennotes 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: ['listennotes']
    }
);

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

Configure the agent with the MCP URL

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

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

Post episodes by ids

The listennotestest_episodes_post endpoint allows users to retrieve metadata for multiple podcast episodes in a single request.

Create podcast via form data

The listennotestest_podcasts_post endpoint allows users to retrieve information about multiple podcasts using various identifiers such as Listen Notes IDs, RSS feed URLs, Apple Podcasts IDs, or Spotify IDs.

Retrieve curated podcast by id

Retrieves detailed information about a specific curated podcast using its unique identifier.

Fetch best podcasts list

The getBestPodcasts endpoint retrieves a curated list of the best podcasts from the Listen Notes platform.

Retrieve genre list

The GetGenres endpoint retrieves a comprehensive list of available genres within the listennotestest platform.

Get playlists

Retrieves a list of playlists from the Listen Notes platform.

Listen to just listen endpoint

The 'just_listen' endpoint is a basic listener or health check mechanism for the listennotestest app.

Get podcast audience by id

Retrieves audience information for a specific podcast identified by its unique ID.

Get curated podcasts

Retrieves a list of curated podcasts from the Listen Notes platform.

Retrieve episode by id

Retrieves detailed information about a specific episode using its unique identifier.

Fetch Podcast Details And Episodes

Retrieves detailed information about a specific podcast using its unique identifier.

Fetch podcast languages

Retrieves a list of supported languages in the Listen Notes API.

Get podcast domains by name

Retrieves a list of podcasts associated with a specified domain name.

Get episode recommendations by id

Retrieves a list of recommended podcast episodes based on a specific episode ID.

Get podcast recommendations by id

Retrieves a list of podcast recommendations based on a specified podcast ID.

Fetch related searches data

Retrieves a list of related search queries based on the current context or user's recent search activity.

Fetch Supported Regions

Retrieves information about available regions in the listennotestest platform.

Retrieve trending searches

Retrieves a list of currently trending search terms related to podcasts.

Search Episode Titles

The search_episode_titles endpoint allows users to search for and retrieve episode titles based on specified criteria.

Search operation endpoint

The search endpoint allows users to query notifications or events within the listennotestest platform.

Fetch Playlist Info

Retrieves detailed information about a specific playlist using its unique identifier.

Post podcast rss by id

Retrieves or generates an RSS feed for a specific podcast identified by its unique ID.

Delete podcast by id

Deletes a specific podcast from the system based on its unique identifier.

Spell check retrieval

The spellcheck endpoint provides a spell-checking service for text input.

Submit podcast rss url

The submit_podcast endpoint allows users to submit a podcast for inclusion in the Listen Notes database.

Get typeahead suggestions

The typeahead endpoint provides real-time search suggestions as users type their queries.

FRAMEWORKS

How to build Listennotes MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Listennotes MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Listennotes MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Listennotes MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Listennotes MCP with Claude Cowork

Codex logo

Codex

Use Listennotes MCP with Codex

OpenClaw logo

OpenClaw

Use Listennotes MCP with OpenClaw

Hermes logo

Hermes

Use Listennotes MCP with Hermes

CLI logo

CLI

Use Listennotes MCP with CLI

Google ADK logo

Google ADK

Use Listennotes MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Listennotes MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Listennotes MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Listennotes MCP with LlamaIndex

CrewAI logo

CrewAI

Use Listennotes MCP with CrewAI

FAQ

Frequently asked questions

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

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

Start with Listennotes.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies