MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
제작자가 쓴 설명(영어 원문)
SEO for agencies: rank tracking, site audits, Search Console, GA4, backlinks and AI visibility.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://seolyticize.com/api/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http seolyticize https://seolyticize.com/api/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"seolyticize": {
"url": "https://seolyticize.com/api/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"seolyticize": {
"type": "http",
"url": "https://seolyticize.com/api/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://seolyticize.com/api/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 seolyticize.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 12일 전 레지스트리에 올라왔어요.
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, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
SEO workflows for coding and chat agents, over the Seolyticize MCP server. Every skill is a folder with a SKILL.md in the open Agent Skills format, so the same files work in Claude, Codex, Cursor, GitHub Copilot, Gemini and Antigravity, Kiro, Cline, OpenCode, Goose and any other agent that reads them.
| Skill | Use it for |
|---|---|
ai-visibility-audit | Audit a client's visibility in AI assistants with Seolyticize. Covers whether ChatGPT, Claude, Perplexity, Gemini, Copilot and Google AI Overviews or AI Mode recommend the client, which rivals and sources they name instead, GEO readiness per engine, agent readiness (llms.txt, AI crawler access) and the brand entity, then what to change. Keeps measured citations apart from readiness heuristics. Use for "AI visibility", "are we in ChatGPT", "GEO audit", "LLM SEO", "why don't assistants recommend us". |
alerts-and-monitoring | Set up and run monitoring for a Seolyticize client - alert rules and where they deliver (email, Slack, webhook, Telegram), the default alerts, crawl schedules, deploy checks and deploy hooks, change detection between crawls, traffic anomalies, signed webhooks for events, and the weekly digest. Use for "tell me when rankings drop", "set up alerts", "this alert is too noisy", "crawl nightly", "did the release break anything", "send events to our system" or "why didn't my webhook fire". |
analytics-and-conversions | Measure what search earns a Seolyticize client - read Search Console and GA4, install the cookieless first-party analytics snippet, define goals and funnels, collect server-side with issue_server_collect_key and visit tokens, record orders from any store with record_order / record_orders, and attribute revenue with get_seo_revenue. Use for "set up tracking", "what did organic earn", "count sign-ups", "which pages make money", "track AI agents server-side", "log orders against visits" or "what is SEO worth". |
client-onboarding | Set up a new SEO client in Seolyticize end to end - create the client, write its brief from the website, connect Search Console, GA4 and first-party analytics, add the default alerts, schedule crawls, run the first crawl and start rank tracking, then confirm with get_next_steps. Use when someone says "onboard a new client", "add a client", "set up acme.com", "we just signed X" or "connect their Search Console". |
competitor-analysis | Work out who a Seolyticize client really competes with in search and where each rival wins. Covers search competitors and share of voice, keyword, content and link gaps, what competitors just published or changed, and which brands AI assistants name and cite instead of the client. Use for "competitor analysis", "who are we up against", "why is X beating us", "competitor gap", "what are competitors publishing", "share of voice", "who does ChatGPT recommend". |
content-brief-and-write | Brief, draft, score and fix a page for a Seolyticize client. Profile what ranks, build a content brief for the right page type, draft or rewrite sections, then score the draft for coverage, draft quality, keyword placement, E-E-A-T and page-type fit against the results page. Also covers comparison pages and checks on programmatic template pages. Use for "write a brief", "draft an article", "is this ready to publish", "score this content", "why doesn't this page rank", "write a vs page", "are our location pages thin". |
content-opportunities | Decide which content work to do first for a Seolyticize client. Covers pages close to the top three, decaying and stale pages, pages cannibalising each other, competitor topic gaps, topical authority and templated meta descriptions. Ends in a prioritised plan of updates, merges and new pages. Use for "content plan", "what should we write or update", "quick wins", "content audit", "why is this page losing traffic", "what to refresh this month". |
deploy-check | Check a release for SEO damage before and after it ships, with Seolyticize. Runs check_deploy against a deploy preview or staging, compare_sites between staging and production (including www/apex redirect behaviour), sets up the GitHub Action that fails a pull request, and watches for rollback signals after release. Use for "will this deploy hurt SEO", "check the preview", "is staging ready to go live", "did the release noindex anything", "SEO check in CI", "should we roll back". |
keyword-research | Research and shortlist keywords for a Seolyticize client. Start from near-misses the site already ranks 4–20 for in Search Console, expand seeds within a quoted budget, judge difficulty for this site from the real results page, check intent, cluster, forecast, then save the shortlist and the page that owns each keyword. Use for "keyword research", "find keywords", "what should we target", "content ideas", "which keywords can we win". |
link-building | Find, win and keep links for a Seolyticize client. Prospects come from competitors' linkers, broken and lost links to reclaim, unlinked mentions, resource pages and journalist requests, with outreach previewed as a dry run before anything is sent. Also checks link health — profile score by industry, toxic links and whether to disavow, velocity red flags and link networks. Use for "link building", "backlink prospects", "outreach", "lost links", "toxic backlinks", "should we disavow", "link profile health", "journalist requests". |
local-seo | Audit and improve a business's local search with Seolyticize. Covers the local SEO audit with its Google Business Profile checklist and duplicate listings, map-pack grid scans (sizes, cost, share of local voice), NAP consistency and directory citations, and reviews across Google, Tripadvisor and Trustpilot, with reply drafts that respect healthcare and legal rules. Also changes the listing itself (hours, description, phone, website, categories, attributes) and publishes posts on it, previewed as a dry run first. Use for "local SEO audit", "map pack", "grid scan", "Google Business Profile", "NAP", "citations", "reply to our reviews", "update our opening hours", "post on our Google listing". |
monthly-client-report | Write and deliver the monthly SEO report a client actually reads - what changed, why, what it earned and what happens next - from Seolyticize evidence (one get_report_data read for the period first), following the agency's report template, saved as a written report, and sent or scheduled. Covers report templates, saved data reports, schedules, sending, and share links (listing and revoking them too) only when asked. Use for "monthly report", "client update", "write up October's results", "send Acme their report" or "make this our report format". |
rank-tracking-review | Review how a Seolyticize client's tracked keywords moved and why. Covers positions and their spread, ranking-URL swaps, SERP features and AI Overviews, Google AI Mode citations, the desktop and mobile split, volatility, Google updates and timeline annotations, with what to do about each pattern. Use for "how are rankings", "what dropped", "rank report", "why did we lose positions", "is it us or Google", "do we show in AI Mode". |
seo-audit-fix | For a coding agent working inside a website's own repository. It turns a Seolyticize audit into code changes — map each issue to the template and file that renders it, fix it, verify on the preview and the live site with check_deploy and compare_sites, then tell search engines which URLs changed. Covers Next.js, WordPress, Shopify themes and plain HTML. Use for "fix the SEO issues", "fix the audit in the code", "why is this page not indexed", "fix our canonicals/titles/schema". |
seo-weekly-loop | Run the weekly SEO check-in for one client with Seolyticize. Covers what moved (rankings, Search Console, analytics and revenue, audit diffs, alerts), why it moved, this week's three to five actions, and a short plain-words note for the client. Starts from get_next_steps and the client brief, and records the week in the brief. Use for "weekly SEO check", "what changed this week", "Monday review", "what should we work on this week", "weekly client update". |
seolyticize | The foundation for any work with Seolyticize, the SEO platform for agencies. How to connect (hosted MCP server, API key, CLI, TypeScript/Python/Go SDKs), the rules every call follows (money, dryRun, quotes, idempotency, strict arguments, error codes with next steps, honest nulls), and which task skill to load next. Use whenever a request mentions Seolyticize, an SEO client, "connect to Seolyticize", "which tool do I use", or any SEO job run through it. |
spend-and-costs | Control and explain what Seolyticize spends on the agency's own DataForSEO and AI vendor accounts - quote calls before making them, set client budgets and alerts, read a budget and its month-end forecast with get_budget_status, read get_costs and get_client_costs, reconcile the vendor balance with get_vendor_reconciliation and explain any gap, and keep paid calls low. Use for "how much will this cost", "cap this client at $50", "what are we spending", "how much budget is left", "will this client go over", "which client costs most", "why did our DataForSEO balance drop" or "cut our data costs". |
technical-audit | Run and triage a technical SEO audit of a client's site with Seolyticize. Crawl, rank issues by impact, check index coverage, URL inspection, sitemaps, Core Web Vitals (field and lab), JavaScript rendering, structured data, hreflang and agent readiness, then accept the intentional findings, route fixes to owners and turn the rest into tasks grouped by template. Use for "audit the site", "technical SEO audit", "why isn't it indexed", "what is broken on the site", "crawl the site". |
The skills call Seolyticize's tools, so the agent needs the server: https://seolyticize.com/api/mcp (Streamable HTTP). The first call opens a browser to sign in and choose which agency, role and clients the agent may use. Where a browser is not available (CI, a headless box), use an API key from Settings → API keys as Authorization: Bearer $SEOLYTICIZE_API_KEY, or the CLI's stdio bridge: npx -y @seolyticize/cli mcp.
npx skillsnpx skills add Seolyticize/skills # pick the agents to install for
npx skills add Seolyticize/skills -g --all # every skill, every agent, for your user
/plugin marketplace add Seolyticize/skills
/plugin install seolyticize@seolyticize
The plugin brings the skills and the server. Skills only: copy skills/* into ~/.claude/skills/, and add the server with claude mcp add --transport http seolyticize https://seolyticize.com/api/mcp.
Download a skill's zip from the latest release — for example seolyticize.zip — and upload it under Customize → Skills (+), or Settings → Capabilities → Upload skill in older apps; custom skills need a paid plan with code execution on. Add Seolyticize as a custom connector (`http
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요