MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
LinkedIn, Sales Navigator, Recruiter, WhatsApp, Instagram, Telegram and email MCP for coding agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
X-API-KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http unipile 'https://developer.unipile.com/mcp?branch={branch}' --header 'X-API-KEY: your-value'Fill in the empty values before running it.
The address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"unipile": {
"url": "https://developer.unipile.com/mcp?branch={branch}",
"headers": {
"X-API-KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
The address contains {…} parts that only you know (such as your account), so copy it and fill them in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"unipile": {
"type": "http",
"url": "https://developer.unipile.com/mcp?branch={branch}",
"headers": {
"X-API-KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
X-API-KEY secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain unipile.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
The address needs your own account values, so we cannot check it for you
The address needs your own account values, so we cannot check it for you
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: X-API-KEY
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 39 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The Unipile MCP server gives your coding agent a LinkedIn MCP server (Classic, Sales Navigator and Recruiter), a WhatsApp MCP, an Instagram MCP, a Telegram MCP, an email MCP for Gmail, Outlook and IMAP, and a calendar MCP for Google and Outlook, all in one hosted server. Plug it into Cursor, Claude Code, Codex, Gemini CLI, VS Code or Windsurf. Your agent then reads the exact Unipile API contract, writes your product's LinkedIn, WhatsApp or email integration in your stack, and tests each call on your own connected accounts before you commit.
https://developer.unipile.com/mcp?branch=v2.0
Behind the server is the Unipile API: one REST API for the LinkedIn API, WhatsApp API, Instagram API, Telegram API, email API and calendar API. Your users connect their own accounts, and your product acts on those accounts with one key.
Teams building a SaaS product that needs to talk to its users' LinkedIn, WhatsApp or email accounts:
The MCP server is a build-time tool. Your agent uses it in the editor to discover, write and test the integration. The code it writes calls the Unipile REST API directly, or the Node.js or Python SDK, so your product does not depend on MCP in production.
Building a LinkedIn, WhatsApp or email integration usually means reading API docs page by page and copying request schemas by hand. You also have to learn the provider quirks, such as how a Sales Navigator search differs from a Recruiter one, or how an InMail differs from a message. Then comes trial and error with curl. With the MCP server connected, your agent does that loop itself:
You: Add a "Connect on LinkedIn" button to our CRM contact page. It sends an
invitation with the rep's note and shows whether it is still pending.
Agent: search-endpoints "relation-requests" get-endpoint POST /v2/{account_id}/users/me/relation-requests get-endpoint GET /v2/{account_id}/users/me/relation-requests -> writes the service, the route handler and the UI state in your codebase execute-request sends a real invitation from your test LinkedIn account to a test profile -> checks the response against the schema, then hands you the diff
claude mcp add --transport http unipile "https://developer.unipile.com/mcp?branch=v2.0" --header "X-API-KEY: your-scoped-api-key"
Configs for Cursor, VS Code, Codex, Gemini CLI, Windsurf and Claude Desktop are in Setup.
Every route below is Unipile API v2 and runs on behalf of a connected account: {account_id} is its acc_... ID, from GET /v2/accounts/. This list is a map for you and your agent, not a schema: the agent should call get-endpoint on a route before writing its request body.
| Feature in your product | Route |
|---|---|
| People search with LinkedIn filters (keywords, title, company, location, network distance) | POST /v2/{account_id}/linkedin/search/people |
| Company, post and job search | POST /v2/{account_id}/linkedin/search/companies · /search/posts · /search/jobs |
| Run a search straight from a LinkedIn search URL | POST /v2/{account_id}/linkedin/search |
| Look up filter IDs (locations, industries, companies, schools) | GET /v2/{account_id}/linkedin/search/parameters |
| Profile enrichment: experience, education, skills and other sections | GET /v2/{account_id}/users/{user_id}?with_sections=... |
| Send an invitation (connection request) with a note | POST /v2/{account_id}/users/me/relation-requests |
| List pending invitations, then accept or cancel them | GET /v2/{account_id}/users/me/relation-requests · POST .../{request_id}/accept · POST .../{request_id}/cancel |
| Relations, followers and following | GET /v2/{account_id}/users/{user_id}/relations · /followers · /following |
| Follow or unfollow a profile | POST /v2/{account_id}/users/me/follow/{user_id} · /unfollow/{user_id} |
| Remove a relation | DELETE /v2/{account_id}/users/me/relations/{user_id} |
| Send a LinkedIn message, or an InMail to someone outside the network | POST /v2/{account_id}/chats/send with specifics.linkedin.classic.inmail: true |
| Show remaining InMail credits | GET /v2/{account_id}/linkedin/inmail-credits |
| Company page data, and the pages the user manages | GET /v2/{account_id}/linkedin/company/{company_id} · GET /v2/{account_id}/linkedin/company/pages |
| Endorse a skill | POST /v2/{account_id}/linkedin/member/{member_id}/endorse-skill |
| Publish posts, comment, react; read a profile's activity | Posts and engagement |
| Create, publish and close job postings; read applicants and resumes | POST /v2/{account_id}/linkedin/jobs · POST .../jobs/{job_id}/publish · POST .../jobs/{job_id}/applicants · GET .../applicants/{applicant_id}/resume |
| Call a LinkedIn endpoint that has no dedicated route yet | POST /v2/{account_id}/linkedin/ |
The account needs a Sales Navigator seat. When a user holds several LinkedIn contracts, list them with GET /v2/{account_id}/linkedin/contracts and pick one with POST .../contracts/{contract_id}/select.
| Feature in your product | Route |
|---|---|
| Lead search with Sales Navigator filters (seniority, function, headcount, changed jobs, posted on LinkedIn...) | POST /v2/{account_id}/linkedin/sales-navigator/search/people |
| Account (company) search | POST /v2/{account_id}/linkedin/sales-navigator/search/companies |
| Import a search from a Sales Navigator URL or a saved search | POST /v2/{account_id}/linkedin/sales-navigator/search |
| Look up filter IDs | GET /v2/{account_id}/linkedin/sales-navigator/search/parameters |
| Lead lists: list, browse, save a lead | GET .../sales-navigator/lead-lists · POST .../lead-lists/{list_id} · POST .../lead-lists/{list_id}/save |
| Account lists: list, browse, save an account | GET .../sales-navigator/account-lists · POST .../account-lists/{list_id} · POST .../account-lists/{list_id}/save |
| Profile as Sales Navigator shows it | GET /v2/{account_id}/users/{user_id}?variant=linkedin_sales_navigator |
| Send a Sales Navigator InMail | POST /v2/{account_id}/chats/send with specifics.linkedin.sales_navigator.subject |
The account needs a Recruiter seat.
| Feature in your product | Route |
|---|---|
| Candidate search with Recruiter filters (skills, job title, years of experience, spoken language, workplace type...) | POST /v2/{account_id}/linkedin/recruiter/search/people |
| Import a search from a Recruiter URL or a saved search | POST /v2/{account_id}/linkedin/recruiter/search |
| Look up filter IDs | POST /v2/{account_id}/linkedin/recruiter/search/parameters |
| Candidate profile as Recruiter shows it, with recruiting activity | GET /v2/{account_id}/users/{user_id}?variant=linkedin_recruiter&with_sections=linkedin_recruiting_activity |
| Send a Recruiter InMail (subject, signature, follow-up; InMail or email) | POST /v2/{account_id}/chats/send with specifics.linkedin.recruiter |
| Hiring projects: list, create, edit | GET / POST /v2/{account_id}/linkedin/recruiter/projects · PATCH .../projects/{project_id} |
| Search a project's talent pool | POST .../recruiter/projects/{project_id}/talent-pool/search |
| Pipeline: list candidates, save a candidate to a project | POST .../projects/{project_id}/pipeline · POST .../pipeline/candidate/save |
| Applicants and their resumes | POST .../projects/{project_id}/talent-pool/applicants · GET .../applicants/{applicant_profile_id}/resume |
| Create, publish and close Recruiter job postings; check job slot credits | POST .../recruiter/jobs · POST .../projects/{project_id}/jobs/{job_id}/publish · GET .../recruiter/job-slots-credits |
One set of routes serves every messaging provider: WhatsApp chats and groups, Instagram DMs, Telegram chats and groups, and LinkedIn messages. A unified inbox is one integration, not four.
| Feature in your product | Route |
|---|---|
| Inbox: list chats, or the chats of one inbox | GET /v2/{account_id}/chats · GET /v2/{account_id}/inboxes/{inbox_id}/chats |
| Conversation view: read a chat's messages | GET /v2/{account_id}/chats/{chat_id}/messages |
| Find the existing chat with a contact | GET /v2/{account_id}/users/{user_id}/chat |
| Start a new chat (1:1 or group) with a first message | POST /v2/{account_id}/chats/send |
| Reply in a chat, with attachments | POST /v2/{account_id}/chats/{chat_id}/messages/send |
| Forward, edit, delete, mark as read | POST .../messages/{message_id}/forward · /modify · DELETE .../messages/{message_id} · POST .../read |
| Reactions | POST .../messages/{message_id}/reactions |
| Group chats: add or remove participants | `
Only the beginning is shown; read the rest in the repo