MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
제작자가 쓴 설명(영어 원문)
Self-driving LinkedIn prospecting: it sources, warms and invites daily. You approve every message.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
Authorization비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
터미널에서 이 명령어를 실행하세요
claude mcp add --transport http linkedin https://agent.gtmotto.com/mcp --header 'Authorization: your-value'실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"linkedin": {
"url": "https://agent.gtmotto.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"linkedin": {
"type": "http",
"url": "https://agent.gtmotto.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
Authorization 비밀 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 도메인 gtmotto.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: Authorization
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.2.1)은 지난달 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Give Claude a LinkedIn seat that works while you sleep.
GTM Otto is self-driving LinkedIn prospecting. From Claude, Cursor or ChatGPT you describe who you want to meet; GTM Otto finds them daily, warms them up from your own LinkedIn account (visit, like, comment), invites them, and opens the conversation. Nothing is said without you.
This repository is the public home of the GTM Otto MCP server: the registry manifest (server.json), the Claude Code plugin with eight skills, the tool reference and the onboarding guide. The server itself runs at https://agent.gtmotto.com/mcp (Streamable HTTP).
Release status (2026-09-22): listed on the official MCP Registry as com.gtmotto/linkedin (manifest 1.2.1). https://agent.gtmotto.com/mcp answers initialize with no credentials; OAuth is served at /.well-known/oauth-protected-resource (authorization server clerk.gtmotto.com); 21 tools are deployed, including gtm_connect_linkedin and the three approval tools.
Every other LinkedIn MCP is a remote control for a tool you still have to operate: lists to upload, sequences to build, seats to rotate. GTM Otto is the only one where the outreach keeps running after the chat ends. A play is an ICP plus up to five sourcing lanes plus an autonomy level. The server exposes 21 tools and, deliberately, no send verb: the agent can set up, size, preview, launch, pause and review a play, and it can approve or reject one drafted message at a time, but it cannot write to a stranger on your behalf.
The endpoint is the same everywhere: https://agent.gtmotto.com/mcp.
Authentication. Add the server with no credentials. The first time the agent calls a protected tool, the client shows a Connect card; sign in (or sign up) in the popup and the call is retried. Scripts and clients that cannot do OAuth can send an API key instead: Authorization: Bearer gtm_sk_..., minted at app.gtmotto.com/connect.
Settings, then Connectors, then Add custom connector. Name it GTM Otto, paste https://agent.gtmotto.com/mcp, save. Start a chat and say what you want; the Connect card appears on the first protected call.
claude mcp add --transport http gtmotto https://agent.gtmotto.com/mcp
Then /mcp inside a session to authenticate in the browser. To use an API key instead:
claude mcp add --transport http gtmotto https://agent.gtmotto.com/mcp \
--header "Authorization: Bearer gtm_sk_..."
The deeplink is cursor://anysphere.cursor-deeplink/mcp/install?name=gtmotto&config=eyJ1cmwiOiJodHRwczovL2FnZW50Lmd0bW90dG8uY29tL21jcCJ9, where the config value is the base64 of {"url":"https://agent.gtmotto.com/mcp"}. By hand, add this to .cursor/mcp.json:
{
"mcpServers": { "gtmotto": { "url": "https://agent.gtmotto.com/mcp" } } }
Settings, then Connectors, then Create (developer mode must be on). Name GTM Otto, URL https://agent.gtmotto.com/mcp, authentication OAuth. Enable the connector in a chat from the tools menu.
Any MCP client that speaks Streamable HTTP works: point it at https://agent.gtmotto.com/mcp, with OAuth or the Authorization header above. n8n, Windsurf, VS Code and the reference mcp-remote shim all fit.
The gtm-otto plugin connects the server and adds eight skills that turn a sentence into a running play:
/plugin marketplace add gtmotto/mcp
/plugin install gtm-otto@gtmotto
| Skill | What it does |
|---|---|
launch-a-play | Estimate the ICP, create a draft play, connect LinkedIn, preview each lane, confirm, activate, explain the next 48 hours. |
icp-to-play | A sentence, a URL or a persona into the seven ICP facets, a company count, and a people_search lane on a new draft or an existing play. |
post-discovery | Turn "people complaining about X on LinkedIn" into a Post discovery lane, with a worked French example. |
hiring-signals | "Companies hiring for X" into a Job offers lane that reaches the buyer inside each hiring company, not the recruiter. |
weekly-play-review | Stats, run history and the approval queue folded into a one-page review with concrete changes. |
instantly-to-linkedin | With the Instantly MCP also connected: companies that opened or replied to a campaign become an account list on LinkedIn. |
heyreach-migration | From an exported HeyReach lead list: companies to an account list, facets to the ICP, and an honest note on what does not carry over. |
linkedin-safety-check | Seat state, daily cap and working hours turned into a plain-English health report. |
Each skill names the exact tools and arguments it calls, what to show you, and where it stops to ask.
Full reference with arguments: docs/tools.md.
| Tool | Scope | One line |
|---|---|---|
gtm_whoami | read | Org, plan, lead meter, and the next step to follow. Start here. |
gtm_list_plays | read | Every play with product, status, seat and pipeline spread. |
gtm_show_play | read | One play in full: ICP, lanes, autonomy ladder, cap, working hours, seat. |
gtm_play_stats | read | The pipeline over four windows, each with its delta versus the window before. |
gtm_linkedin_status | read | The play's seat state and today's headroom against LinkedIn's limits. |
gtm_sources_reference | read | The reference for every sourcing lane. Read before configuring one. |
gtm_show_sources | read | All five lanes of a play: config, switch, blockers, last run, memory. |
gtm_source_runs | read | Run history of one lane, newest first. |
gtm_list_approvals | read | Drafted messages waiting for a human, with their approval ids. |
gtm_estimate_icp | write | "About N companies match" for a candidate ICP. Writes nothing. |
gtm_create_play | write | Create a fully configured play. Draft by default; activate flag. |
gtm_update_icp | write | Change a play's seven ICP facets. Only the ones you name. |
gtm_update_play | write | Name, goal, voice, paused, status active or draft, dailyCap, workingHours. |
gtm_configure_source | write | Write a lane's settings (merge). Can switch it on in the same call. |
gtm_set_source | write | Switch a lane on or off. Refused when there is nothing to run on. |
gtm_preview_source | write | Dry-run one lane: size and a 10-person sample. No side effects. |
gtm_run_source | write | Run one lane now. Real leads, real budget. Only when asked. |
gtm_forget_harvested_posts | write | Clear a post lane's memory so a settings change can be re-tested. Costs. |
gtm_connect_linkedin | write | Returns a browser link to connect the LinkedIn seat; then poll gtm_linkedin_status. |
gtm_approve | write | Approve one drafted message by approval id. The client asks you first. |
gtm_reject | write | Reject one drafted message by approval id. The client asks you first. |
gtm_preview_source is free of side effects; gtm_run_source spends real budget and is only called when you asked.account_list, at most 100) and post URLs, never a CSV of individual LinkedIn profiles.server.json registry manifest (com.gtmotto/linkedin)
.claude-plugin/marketplace.json Claude Code marketplace "gtmotto" plugins/gtm-otto/ the plugin: MCP server + eight skills .claude-plugin/plugin.json skills/ /SKILL.md docs/tools.md the 21 tools with arguments docs/onboarding.md the ideal first conversation CHANGELOG.md
com.gtmotto/linkedinThe playbooks that need nothing but LinkedIn (find buyers in comments, ICP to a Sales Navigator search, hiring-signal prospecting by hand, LinkedIn limits, the comment and invite writer) live in gtmotto/gtm-skills. That repository registers no server and needs no account; each of its skills ends with a pointer to the skill here that runs the same recipe daily.
This repository is mirrored out of the GTM Otto monorepo. Issues and pull requests are welcome here and are read; fixes are applied upstream and land in the next mirror, so a PR may be closed with a "merged upstream" note rather than merged in place. Keep prose free of em dashes, and never describe the product as an automated sales rep of any kind: it is self-driving LinkedIn prospecting.
MIT. See LICENSE.