Use
COMPOSIOFOR YOU
Give Claude, Codex, or any harness secure access to 1700+ tools
CLI
One command to add tools and auth to your coding agent
Build
DEVELOPER PLATFORM
SDKs, tools, and auth for agents and backend apps
MCP GATEWAY
One managed MCP endpoint for all your tools and agents
ENTERPRISE
SSO, governance, and audit controls for deploying agents org-wide
Features
TRIGGERS
Start background agents from events across your connected apps
FIREWALLNEW
Blocks instructions hidden in tool results before your agent reads them
INSTANTNEW
Audio, video, search, browser and data tools, with no keys to manage
OPTIMIZATION
Lower cost per completed task with optimised tools and skills
FOR AGENTS
CLAUDE CODEX OPENCLAW CURSOR HERMES
BUILT FOR
OFFICE WORK SALES MARKETING PRODUCT & DESIGN CUSTOMER SUPPORT ENGINEERING HR & RECRUITING FINANCE & OPS E-COMMERCE CONTENT & MEDIA IT & SECURITY
ALL USE CASES
DOCS

How to integrate Happy scribe MCP with Vercel AI SDK v6

Connect Vercel AI SDK v6 to Happy scribe MCP. Transcribe this podcast episode to text, generate subtitles for uploaded video file, and more using natural language, with authentication handled for you.

Get started for free Get a demo

Happy scribe

Api Key

Happy Scribe is an automatic transcription service that converts audio and video files into accurate text. It lets you quickly generate transcripts and subtitles, saving you hours of manual work.

19 Tools

Managed auth

Connect Happy scribe without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Book a call

Explore the MCP Gateway

Introduction

This guide walks you through connecting Happy scribe to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Happy scribe agent that can transcribe audio and video, create subtitles, order translations, export transcripts, and list your transcriptions through natural language commands.

This guide will help you understand how to give your Vercel AI SDK agent real control over a Happy scribe account through Composio's Happy scribe MCP server.

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

Also integrate Happy scribe with

Claude Code Claude Cowork OpenAI Agents SDK Claude Agent SDK Codex OpenClaw Hermes Atomic Agent Google ADK LangChain Mastra AI LlamaIndex CrewAI Pydantic AI AutoGen

TL;DR

Here's what you'll learn:

How to set up and configure a Vercel AI SDK agent with Happy scribe integration
Using Composio's Tool Router to dynamically load and access Happy scribe tools
Creating an MCP client connection using HTTP transport
Building an interactive CLI chat interface with conversation history management
Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

streamText: Core function for streaming responses with real-time tool support
MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
OpenAI Provider: Native integration with OpenAI models

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

The Happy Scribe MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Happy Scribe account. It provides structured and secure access to your transcription and subtitle services, so your agent can perform actions like starting new transcriptions, generating subtitles, exporting files, and managing your transcription jobs on your behalf.

Automated transcription creation: Instantly start new transcription jobs from audio or video files using a simple agent command.
Subtitle generation for videos: Have your agent generate accurate subtitles for your video content for accessibility and localization.
Export and download transcripts or subtitles: Let your agent export completed transcriptions or subtitles in various formats for easy distribution.
Account and usage monitoring: Retrieve account details, subscription status, and API usage statistics to keep tabs on your service limits.
Transcription management and cleanup: Direct your agent to delete completed or unwanted transcription jobs, keeping your workspace organized.

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before you begin, make sure you have:

Node.js and npm installed
A Composio account with API key
An OpenAI API key

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.

Install required dependencies

bash

npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

First, install the necessary packages for your project.

What you're installing:

@ai-sdk/openai: Vercel AI SDK's OpenAI provider
@ai-sdk/mcp: MCP client for Vercel AI SDK
@composio/core: Composio SDK for tool integration
ai: Core Vercel AI SDK
dotenv: Environment variable management

Set up environment variables

bash

OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

OPENAI_API_KEY: Your OpenAI API key for GPT model access
COMPOSIO_API_KEY: Your Composio API key for tool access
COMPOSIO_USER_ID: A unique identifier for the user session

Import required modules and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

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

What's happening:

We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
The dotenv/config import automatically loads environment variables
The MCP client import enables connection to Composio's tool server

Create Tool Router session and initialize MCP client

typescript

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["happy_scribe"],
  });

  const mcpUrl = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Happy scribe tools
The create method takes the user ID and specifies which toolkits should be available
The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
This session provides access to all Happy scribe-related tools through the MCP protocol

Connect to MCP server and retrieve tools

typescript

const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();

What's happening:

We're creating an MCP client that connects to our Composio Tool Router session via HTTP
The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
The type: "http" is important - Composio requires HTTP transport
tools() retrieves all available Happy scribe tools that the agent can use

Initialize conversation and CLI interface

typescript

let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to happy_scribe, like summarize my last 5 emails, send an email, etc... :)))\n",
);

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

rl.prompt();

What's happening:

We initialize an empty messages array to maintain conversation history
A readline interface is created to accept user input from the command line
Instructions are displayed to guide the user on how to interact with the agent

Handle user input and stream responses with real-time tool feedback

typescript

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;
  }

  messages.push({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

We use streamText instead of generateText to stream responses in real-time
toolChoice: "auto" allows the model to decide when to use Happy scribe tools
stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
onStepFinish callback displays which tools are being used in real-time
We iterate through the text stream to create a typewriter effect as the agent responds
The complete response is added to conversation history to maintain context
Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Happy scribe and Vercel AI SDK:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

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

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["happy_scribe"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to happy_scribe, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

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

  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;
    }

    messages.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Happy scribe agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

Real-time streaming responses for a better user experience with typewriter effect
Live tool execution feedback showing which tools are being used as the agent works
Dynamic tool loading through Composio's Tool Router with secure authentication
Multi-step tool execution with configurable step limits (up to 10 steps)
Comprehensive error handling for robust agent execution
Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

TOOLS

Supported Tools

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

Create Subtitle

Creates a transcription job from a publicly accessible media URL, configured for subtitles by default.

Create Translation Task

Creates an AI-powered translation task to translate an existing transcription into another language.

Delete Transcription

Tool to delete a transcription job.

Delete Webhook

Deletes a webhook by its ID.

Get Account Details

Requests Happy Scribe account information, optionally scoped to a specified organization.

Get Supported Languages

Returns a static reference list of language codes and recorded human transcription service availability.

Get API Rate Limit

Returns the documented default transcription-creation rate limit of 200 requests per hour.

Get Signed Upload URL

Tool to get a signed URL for uploading a file to Happy Scribe's S3 storage.

Confirm Order

Tool to confirm a pending order.

Create Translation Order

Tool to create a translation order from an existing transcription.

Export Transcription

Creates an export job for transcription content in supported document, subtitle, video-editing, and other formats.

Get API Version

Identifies the Happy Scribe API version associated with the connection.

Get Error Codes

Returns a static reference list of selected Happy Scribe HTTP error codes and their meanings.

Get Supported Formats

Returns input and output file format lists to help plan transcription or subtitle work.

Get Transcription Details

Tool to retrieve details and status of a specific transcription job.

Get Webhooks

Tool to retrieve webhooks configured for your account.

Retrieve Export

Tool to retrieve information about a specific export.

List Transcriptions

Retrieves a paginated list of transcription jobs for a Happy Scribe organization.

Retrieve Order

Retrieve details of a Happy Scribe order by its ID.

FRAMEWORKS

How to build Happy scribe MCP Agent with another framework

Claude Code

Use Happy scribe MCP with Claude Code

Claude Cowork

Use Happy scribe MCP with Claude Cowork

OpenAI Agents SDK

Use Happy scribe MCP with OpenAI Agents SDK

Claude Agent SDK

Use Happy scribe MCP with Claude Agent SDK

Codex

Use Happy scribe MCP with Codex

OpenClaw

Use Happy scribe MCP with OpenClaw

Hermes

Use Happy scribe MCP with Hermes

Atomic Agent

Use Happy scribe MCP with Atomic Agent

Google ADK

Use Happy scribe MCP with Google ADK

LangChain

Use Happy scribe MCP with LangChain

Mastra AI

Use Happy scribe MCP with Mastra AI

LlamaIndex

Use Happy scribe MCP with LlamaIndex

CrewAI

Use Happy scribe MCP with CrewAI

Pydantic AI

Use Happy scribe MCP with Pydantic AI

AutoGen

Use Happy scribe MCP with AutoGen

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Drive

Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

Google Docs

Oauth2

Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.

ActiveMerge

Api Key

ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster.

Affinda

Api Key

Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.

FAQ

Frequently asked questions

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

Yes, you can. Vercel AI SDK v6 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 Happy scribe tools.

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

Start with Happy scribe.It takes 30 seconds.

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

Start building

How to integrate Happy scribe MCP with Vercel AI SDK v6

Connect Happy scribe without auth hassles

Introduction

Also integrate Happy scribe with

TL;DR

What is Vercel AI SDK?

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

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install required dependencies

Set up environment variables

Import required modules and validate environment

Create Tool Router session and initialize MCP client

Connect to MCP server and retrieve tools

Initialize conversation and CLI interface

Handle user input and stream responses with real-time tool feedback

Complete Code

Conclusion

Supported Tools

How to build Happy scribe MCP Agent with another framework

Claude Code

Claude Cowork

OpenAI Agents SDK

Claude Agent SDK

Codex

OpenClaw

Hermes

Atomic Agent

Google ADK

LangChain

Mastra AI

LlamaIndex

CrewAI

Pydantic AI

AutoGen

Explore Other Toolkits

Google Drive

Google Docs

ActiveMerge

Affinda

Frequently asked questions

What are the differences in Tool Router MCP and Happy scribe MCP?+

Can I use Tool Router MCP with Vercel AI SDK v6?+

Can I manage the permissions and scopes for Happy scribe while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Happy scribe.It takes 30 seconds.