# How to integrate Happy scribe MCP with Autogen ```json { "title": "How to integrate Happy scribe MCP with Autogen", "toolkit": "Happy scribe", "toolkit_slug": "happy_scribe", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/happy_scribe/framework/autogen", "markdown_url": "https://composio.dev/toolkits/happy_scribe/framework/autogen.md", "updated_at": "2026-05-12T10:14:37.015Z" } ``` ## Introduction This guide walks you through connecting Happy scribe to AutoGen using the Composio tool router. By the end, you'll have a working Happy scribe agent that can transcribe this podcast episode to text, generate subtitles for uploaded video file, export subtitles in srt format for review through natural language commands. This guide will help you understand how to give your AutoGen 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/happy_scribe/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/happy_scribe/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/happy_scribe/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/happy_scribe/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/happy_scribe/framework/codex) - [OpenClaw](https://composio.dev/toolkits/happy_scribe/framework/openclaw) - [Hermes](https://composio.dev/toolkits/happy_scribe/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/happy_scribe/framework/cli) - [Google ADK](https://composio.dev/toolkits/happy_scribe/framework/google-adk) - [LangChain](https://composio.dev/toolkits/happy_scribe/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/happy_scribe/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/happy_scribe/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/happy_scribe/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/happy_scribe/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Happy scribe - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Happy scribe tools - Run a live chat loop where you ask the agent to perform Happy scribe operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `HAPPY_SCRIBE_CREATE_SUBTITLE` | Create Subtitle | Create subtitles for a video file using Happy Scribe's automatic transcription service. Submits a video URL to be processed for subtitle generation. The video must be publicly accessible during ingestion. Returns a subtitle job with an editor URL for reviewing and editing the generated subtitles. Processing states progress from 'initial' -> 'ingesting' -> 'automatic_done' (or 'failed'). Use the GET transcription endpoint to check processing status. | | `HAPPY_SCRIBE_CREATE_TRANSLATION_TASK` | Create Translation Task | Creates an AI-powered translation task to translate an existing transcription into another language. Use this after a transcription is complete (state='automatic_done') to translate it. The task runs asynchronously - use Retrieve Translation Task to check progress and get results. Note: Not all language pairs are supported (e.g., German to English may fail). | | `HAPPY_SCRIBE_DELETE_TRANSCRIPTION` | Delete Transcription | Tool to delete a transcription job. Use when you have a transcription ID and want to remove it, optionally permanently. Use after confirming the transcription ID. | | `HAPPY_SCRIBE_DELETE_WEBHOOK` | Delete Webhook | Deletes a webhook by its ID. This action is idempotent: if the webhook does not exist or was already deleted, it returns success. Use Get Webhooks to retrieve available webhook IDs. | | `HAPPY_SCRIBE_GET_ACCOUNT_DETAILS` | Get Account Details | Tool to retrieve details about your account, including subscription status and usage statistics. Use after authenticating your API key to monitor plan and usage. | | `HAPPY_SCRIBE_GET_LANGUAGE_LIST` | Get Supported Languages | Retrieve the list of supported language codes for Happy Scribe transcription services. Returns BCP-47 language codes and indicates which languages have human transcription service available. This is a static reference based on Happy Scribe's official documentation, as there is no dedicated languages API endpoint. | | `HAPPY_SCRIBE_GET_RATE_LIMIT` | Get API Rate Limit | Get Happy Scribe API rate limit information. Returns the documented rate limit for the Happy Scribe API: - Default limit: 200 requests per hour - Applies only to the transcription creation endpoint - When rate limited, API returns HTTP 429 with 'retry_in_seconds' in the body Note: Happy Scribe does not expose rate limit headers, so this tool provides documented defaults. If you encounter a 429 response during transcription creation, wait for the 'retry_in_seconds' value before retrying. For higher limits, contact sales@happyscribe.co with subject "Happy Scribe for Business". | | `HAPPY_SCRIBE_GET_SIGNED_UPLOAD_URL` | Get Signed Upload URL | Tool to get a signed URL for uploading a file to Happy Scribe's S3 storage. Use before creating a transcription or order to obtain a secure upload URL for your media file. | | `HAPPY_SCRIBE_HS_CONFIRM_ORDER` | Confirm Order | Tool to confirm a pending order. Use after creating an order with confirm=false when you're ready to submit it for processing. | | `HAPPY_SCRIBE_HS_CREATE_TRANSLATION_ORDER` | Create Translation Order | Tool to create a translation order from an existing transcription. Use when you have a completed transcription and want translations into one or more languages. By default, the order remains incomplete unless confirm=true. | | `HAPPY_SCRIBE_HS_EXPORT_TRANSCRIPTION` | Export Transcription | Creates an export job to download transcription content in various formats. Use this action after a transcription job completes (state='automatic_done'). First obtain transcription IDs using the List Transcriptions action. The export job runs asynchronously - poll the Retrieve Export action with the returned export ID to check when the download URL becomes available (state='ready'). Supported formats: - Documents: txt, docx, pdf (support timestamps, speakers, comments, highlights) - Subtitles: srt, vtt, stl (standard caption formats) - Video editing: avid, premiere, fcp (professional editing software) - Other: html, json, maxqda | | `HAPPY_SCRIBE_HS_GET_API_VERSION` | Get API Version | Tool to retrieve current API version and check for updates. If Happy Scribe does not expose a dedicated /version endpoint, this tool attempts to infer the version from HTTP response headers or from the base_url path (e.g., /api/v1). | | `HAPPY_SCRIBE_HS_GET_ERROR_CODES` | Get Error Codes | Returns a list of HTTP error codes used by the Happy Scribe API along with their descriptions. Use this tool to understand what different error responses mean when calling other Happy Scribe API endpoints. This returns static reference data matching the official Happy Scribe API documentation. | | `HAPPY_SCRIBE_HS_GET_SUPPORTED_FORMATS` | Get Supported Formats | Tool to retrieve supported file formats. Use when you need to know available input and output formats before creating a transcription or subtitle. If a dedicated '/formats' endpoint is unavailable, this action probes known endpoints to verify connectivity and returns a curated list based on official documentation. | | `HAPPY_SCRIBE_HS_GET_TRANSCRIPTION` | Get Transcription Details | Tool to retrieve details and status of a specific transcription job. Use after creating or listing transcription jobs to inspect a particular job's metadata. | | `HAPPY_SCRIBE_HS_GET_WEBHOOKS` | Get Webhooks | Tool to retrieve webhooks configured for your account. Note: Happy Scribe's public API does not have a dedicated webhooks listing endpoint. Webhooks are specified via webhook_url when creating orders. This action attempts common endpoints and returns an empty list if unavailable. | | `HAPPY_SCRIBE_HS_RETRIEVE_EXPORT` | Retrieve Export | Tool to retrieve information about a specific export. Use when you need to check export status and get download link. | | `HAPPY_SCRIBE_LIST_TRANSCRIPTIONS` | List Transcriptions | Retrieves a paginated list of transcription jobs for a Happy Scribe organization. Returns transcription metadata including ID, name, processing state, language, and duration. Supports filtering by folder and tags, with pagination for large result sets. Note: This returns metadata only; use the Export Transcription action to get actual transcript content. | | `HAPPY_SCRIBE_RETRIEVE_ORDER` | Retrieve Order | Retrieve details of a Happy Scribe order by its ID. Returns order state, pricing, operations, and inputs. Use this to check order status, verify pricing details, or get information about translation/transcription operations. The order ID is obtained from create order responses (e.g., Create Translation Order). | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Happy scribe MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Happy scribe. Instead of manually wiring Happy scribe APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Happy scribe account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Happy scribe via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Happy scribe connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Happy scribe tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Happy scribe session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["happy_scribe"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Happy scribe tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Happy scribe assistant agent with MCP tools agent = AssistantAgent( name="happy_scribe_assistant", description="An AI assistant that helps with Happy scribe operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Happy scribe tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Happy scribe related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Happy scribe session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["happy_scribe"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Happy scribe assistant agent with MCP tools agent = AssistantAgent( name="happy_scribe_assistant", description="An AI assistant that helps with Happy scribe operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Happy scribe related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Happy scribe through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Happy scribe, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build Happy scribe MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/happy_scribe/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/happy_scribe/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/happy_scribe/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/happy_scribe/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/happy_scribe/framework/codex) - [OpenClaw](https://composio.dev/toolkits/happy_scribe/framework/openclaw) - [Hermes](https://composio.dev/toolkits/happy_scribe/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/happy_scribe/framework/cli) - [Google ADK](https://composio.dev/toolkits/happy_scribe/framework/google-adk) - [LangChain](https://composio.dev/toolkits/happy_scribe/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/happy_scribe/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/happy_scribe/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/happy_scribe/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/happy_scribe/framework/crew-ai) ## Related Toolkits - [Google Drive](https://composio.dev/toolkits/googledrive) - 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](https://composio.dev/toolkits/googledocs) - 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. - [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization. - [Affinda](https://composio.dev/toolkits/affinda) - 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. - [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease. - [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training. - [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses. - [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files. - [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently. - [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price. - [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere. - [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code. - [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more. - [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place. - [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work. - [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems. - [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project. - [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks. - [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API. - [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Happy scribe MCP? 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. ### Can I use Tool Router MCP with Autogen? Yes, you can. Autogen 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. ### Can I manage the permissions and scopes for Happy scribe while using Tool Router? 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. ### How safe is my data with Composio Tool Router? 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)