MCP Server Integration
Connect Transcript LOL to your AI agent to search, access, and organise all your recordings
Written By Praveen Pendyala
Last updated About 15 hours ago
Introduction
Transcript LOL provides a remote MCP (Model Context Protocol) server that lets AI assistants like Claude and ChatGPT search your recordings, read transcripts and insights, organise folders, manage speakers, and more β directly from a conversation.
Connect to Claude
Custom connectors are available on Claude's Free, Pro, Max, Team, and Enterprise plans (Free users are limited to one custom connector).
You can see latest documentation from Claude here.
On Pro, Max, or Free plans:
Open Claude (web or desktop) and go to Settings β Connectors
Click the "+" button next to Connectors and choose Add custom connector
Give it a name (e.g., Transcript LOL) and paste the server URL:
https://transcript.lol/api/mcp/mcpClick "Add" to finish configuring the connector
When prompted, sign in with your Transcript LOL account to authorize access
On Team or Enterprise plans:
An owner must add the connector first via Organisation Settings β Connectors, then each member connects individually β find the connector labeled "Custom" in the list and click "Connect" to authenticate.
Using it in a chat
Enable connectors for individual conversations via the "+" button in the lower left of the chat interface, then "Connectors" β you'll see your configured connectors with toggles to enable or disable them per conversation.
Try asking: "Search my recordings for any mention of the Q3 roadmap."
Connect to ChatGPT
To use MCP servers in regular ChatGPT conversations, you must first enable Developer Mode, which is available for ChatGPT Pro, Team, Enterprise, and Edu users.
You can see the latest documentation from ChatGPT here
Enable Developer Mode
Open ChatGPT and click your profile icon, then Settings
Go to Apps & Connectors β Advanced Settings and toggle Developer Mode on
Add Transcript LOL
In ChatGPT, navigate to Settings β Connectors β Create
Fill in the details:
Name: Transcript LOL
Description: Search, read, and organise my meeting recordings and transcripts
Connector URL: the public MCP endpoint of the server β
https://transcript.lol/api/mcp/mcp
Click Create β if the connection succeeds, you'll see a list of the tools the server provides
Sign in with your Transcript LOL account when prompted
Using it in a chat
Open a new chat, click the "+" icon in the message compose area, and select More β Developer mode
Toggle the Transcript LOL connector on for the conversation
Ask away β for example: "Pull the transcript from my last recording and summarise the action items."
Note: ChatGPT requires manual confirmation before write actions can be taken β so when you ask it to move recordings or assign speakers, it will show you the action and ask you to confirm first.
Connect to MCP client
Transcript LOL works with any client that supports remote MCP servers over Streamable HTTP β including Cursor, VS Code, Claude Code, and others.
You'll typically need just two things:
Server URL:
https://transcript.lol/api/mcp/mcpAuthentication: OAuth (the client will open a browser window for you to sign in with your Transcript LOL account)
Consult your client's documentation for where to add a remote MCP server. For example, in Claude Code you can add it from the terminal:
claude mcp add --transport http transcript-lol https://transcript.lol/api/mcp/mcpWhat can the agent do once connected?
Search your recordings with semantic or exact matching, filtered by speaker, folder, or date
Read full transcripts, translations, and AI-generated insights
Organize β create folders and move recordings between them
Manage speakers β create speakers, detect who's speaking from transcript context, and assign labels
Create insight prompts and save them to your workspace
Troubleshooting
Connection fails when adding the connector β check that you've entered the URL exactly, including the full path.
Agent says it can't find any recordings β make sure you authorised with the correct Transcript LOL account, and that the connector is toggled on for the current conversation.
Tools aren't appearing β remove the connector and re-add it; clients cache the tool list at connection time, so a re-add picks up newly released tools.