SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Lmnt MCP with Claude Agent SDK

Connect Claude Agent SDK to Lmnt MCP. Generate a podcast intro in a new voice, list all available ai voices for selection, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Lmnt logoLmnt
Api Key

Lmnt is an AI-powered audio and voice manipulation platform for creative and technical sound work. It makes generating and transforming audio fast, flexible, and accessible for every developer.

8 Tools

Introduction

This guide walks you through connecting Lmnt to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Lmnt agent that can synthesize speech, create and update custom voices, list available voices, and check your account through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Lmnt account through Composio's Lmnt MCP server.

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

Also integrate Lmnt with

Claude CodeClaude CoworkOpenAI Agents SDKMuseCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Lmnt
  • Configure an AI agent that can use Lmnt as a tool
  • Run a live chat session where you can ask the agent to perform Lmnt operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Lmnt MCP server, and what's possible with it?

The LMNT MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your LMNT account. It provides structured and secure access to your LMNT voices, speech generation, and account information, so your agent can generate speech, create custom voices, review available voices, manage voice details, and monitor usage on your behalf.

  • AI speech generation: Have your agent turn text into spoken audio using an available LMNT voice.
  • Speech timing metadata: Instruct your agent to generate speech with word-level timing details for captions, narration, or synchronized media.
  • Custom voice creation: Let the agent create a custom voice from your uploaded audio samples.
  • Voice library management: Direct your agent to list available voices, review voice details and language support, update voice information, or delete voices you no longer need.
  • Account and usage checks: Have your agent retrieve your subscription plan details and current usage statistics.

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Lmnt account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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 @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Lmnt functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Lmnt
  const session = await composio.create(USER_ID, {
    toolkits: ['lmnt'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Lmnt
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Lmnt tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Lmnt
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Lmnt and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['lmnt']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Lmnt tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Lmnt through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Create Voice

Creates a custom LMNT voice from uploaded audio, returning the voice ID and metadata; the voice may initially be in training before becoming ready.

Delete Voice Info

Deletes a custom voice by ID from your LMNT account to manage your voice library.

Generate Speech With Metadata

Generates speech from text and returns base64-encoded audio, a seed, and optional word-level timing metadata.

Get Account

Retrieves account information including subscription plan details and current usage statistics.

Get Voice Info

Gets metadata for a specific LMNT voice, including its ID, name, owner, and training state.

Get Voices List

Retrieves available LMNT voices, with ownership and starred filters and details such as ID, name, state, and optional preview URL.

Synthesize Speech

Synthesizes speech from text of up to 5,000 characters using a specified LMNT voice.

Update Voice Info

Updates a specific LMNT voice's name, description, gender, starred status, or unfreeze state; only user-owned voices can have their name, description, and gender updated, and system voices can only be starred or unstarred.

FRAMEWORKS

How to build Lmnt MCP Agent with another framework

Claude Code logo

Claude Code

Use Lmnt MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Lmnt MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Lmnt MCP with OpenAI Agents SDK

Muse logo

Muse

Use Lmnt MCP with Muse

Codex logo

Codex

Use Lmnt MCP with Codex

OpenClaw logo

OpenClaw

Use Lmnt MCP with OpenClaw

Hermes logo

Hermes

Use Lmnt MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Lmnt MCP with Atomic Agent

Google ADK logo

Google ADK

Use Lmnt MCP with Google ADK

LangChain logo

LangChain

Use Lmnt MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Lmnt MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Lmnt MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Lmnt MCP with LlamaIndex

CrewAI logo

CrewAI

Use Lmnt MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Lmnt MCP with Pydantic AI

AutoGen logo

AutoGen

Use Lmnt MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Lmnt MCP server, the agents and LLMs can only access a fixed set of Lmnt tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Lmnt and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK 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 Lmnt tools.

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

Start with Lmnt.It takes 30 seconds.

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

Start building