MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI 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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://seoskill.dev/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"seo": {
"command": "npx",
"args": [
"-y",
"seo",
"mcp",
"serve"
]
}
}
}Run this in your terminal
claude mcp add --transport http seo https://seoskill.dev/mcpclaude mcp add seo -- npx -y seo mcp servePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"seo": {
"url": "https://seoskill.dev/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"seo": {
"command": "npx",
"args": [
"-y",
"seo",
"mcp",
"serve"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"seo": {
"type": "http",
"url": "https://seoskill.dev/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"seo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"seo",
"mcp",
"serve"
]
}
}
}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.
ChatGPT connects only to servers on the internet:
https://seoskill.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These 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 6, 2026
The publisher (seoskill.dev) is not the repo owner (iannuttall); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
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 0 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 21 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 SEO data I give my agents every day, so they work from my real numbers instead of guessing.
Most AI SEO tools do one of two things. They hand your agent a checklist of generic advice, or they feed it estimates from a keyword tool that has never seen your site. Either way you end up with the same pages everyone else is publishing. Pages written from a keyword list aren't SEO. They're slop.
This works the other way round. It's a Google Search Console MCP server and CLI, and it doesn't tell your agent what to do. It gives it the facts: your clicks, impressions and positions from Search Console, your visits from Google Analytics or Clicky, your Bing data, the dates of Google updates, and a crawl of your site. Your agent works out what matters, and you decide what changes.
It's free and open source. Hack around with it. Make it your own.
Claude Code
claude mcp add --transport http seoskill https://seoskill.dev/mcp
Codex
codex mcp add seoskill --url https://seoskill.dev/mcp
Any other agent
Add https://seoskill.dev/mcp as a remote MCP server. Cursor, Claude Desktop, VS Code and most other agents support it.
The CLI (for crawls and Bing, which run on your machine)
npm i -g seo
seo start
seo start signs you in, connects your agents and installs the skill.
Your agent opens a Google sign-in. Pick the account that can see your Search Console. That's your account. There's no password and no signup form.
Why did clicks drop on example.com last month?
That's it. You're ready to go.
Your agent picks the commands, reads the results and shows you what it found.
I built this because agents kept failing at SEO in the same few ways.
The problem. Ask an agent why your traffic dropped and you get a tidy list of possible causes. Algorithm update, technical issues, content quality. None of it comes from your site, so none of it helps.
The fix is to give it your numbers:
seo report shows your totals against the last period, the pages and queries that moved, and the places worth a look: quick wins, low click-through rates, pages stuck on page two, decay and cannibalization.seo compare lines up the weeks before and after a date, with the Google updates in between.The problem. Ahrefs and Semrush estimate your traffic from a sample. They miss most of the long tail, and they rarely agree with each other.
The fix is to start from your own data. Search Console is the source of truth for Google. When you do need keyword volumes or competitor data, seo research uses your own DataForSEO or Ahrefs key, and it keeps those estimates apart from your real numbers.
The problem. Agents trust their own edits. Then you find the page is still noindexed, still redirecting, or still not in Google.
The fix is to check the live site:
seo page loads one URL and asks Google whether it's indexed.seo index checks every page that lost its clicks.seo crawl checks the whole site, including what AI agents can read.The problem. SEO tools love reports. The first version of this had about 70 of them, and almost nobody used most of them.
The fix was to cut it down to a handful of commands. Each one takes a site or a URL, and dates if you want them. There are no settings to tune. Every result ends with the command to run next, so your agent always knows where to go.
| Command | What it returns |
|---|---|
seo report | Your Search Console overview for --site, then the top rows of each section |
seo page | One URL: the live page, its Google index status and its queries |
seo compare | Before and after a date, with Google updates |
seo index | Google's indexing reasons for known URLs, labelled from live checks, and pages that lost their clicks |
seo research | Keywords, search results, competitors and backlinks from your own key |
seo data | Raw Search Console or Bing rows |
seo analytics | Landing pages from Google Analytics or Clicky |
seo crawl | Technical issues and AI agent access across a site (CLI only) |
seo internal-links | Internal links to add across a site or to one page (CLI only) |
Every command is also an MCP tool, such as seo_report. Add --json to any command when you're scripting it.
As little as possible. The hosted server keeps your linked Google accounts and any keys you save, encrypted. It doesn't keep your Search Console data, your reports or request logs. The CLI keeps your sign-in in your system keychain. The privacy policy has the details.
Apache-2.0. The name and artwork are covered by the brand policy.