MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"searchdock-cli": {
"command": "npx",
"args": [
"-y",
"searchdock-cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add searchdock-cli -- npx -y searchdock-cli mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"searchdock-cli": {
"command": "npx",
"args": [
"-y",
"searchdock-cli",
"mcp"
]
}
}
}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": {
"searchdock-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"searchdock-cli",
"mcp"
]
}
}
}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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 registry name was verified with the GitHub account xplormityai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 26 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
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.
Read Google Search Console analytics, inspect indexed URLs, and monitor sitemaps from your terminal or AI agent.
SearchDock is open source, runs locally, and requests read-only Google access. Use the same core through npm, Python, MCP, a Codex or Claude Code plugin, or a standalone agent skill. Bing Webmaster Tools support is planned.
Copy this prompt into your coding agent:
Set up SearchDock CLI for this project using
https://github.com/xplormityai/searchdock-cli. Read its README and skills/searchdock-setup/SKILL.md. Check Node.js 22+, reuse an existing installation, or install the CLI from npm. Install searchdock-setup and searchdock skills for the agent I am using, scoped to this project, and connect the stdio MCP server if this agent supports it. Keep existing agent configuration. For Google access, ask only for the local path to my Desktop OAuth client JSON and guide me through read-only browser consent. Never print credentials or tokens. Let me choose the Search Console property, then verify the connection with a metrics request. Tell me exactly which steps succeeded and what still needs my input.
Node.js 22 or later is required for every distribution.
# npm
npm install --global searchdock-cli searchdock --help
npx --yes searchdock-cli@0.1.3 --help
pipx install searchdock-cli
The Python package is a launcher containing the exact same JavaScript runtime. It has no separate Google implementation. If you install both packages, use python -m searchdock_cli to select the Python launcher explicitly.
Install both skills for Codex in the current project:
npx --yes skills add xplormityai/searchdock-cli --skill searchdock-setup searchdock --agent codex --copy --yes
Replace codex with claude-code, cursor, opencode, or your supported agent. Add --global only for installation across projects. Skills do not install the CLI or authorize Google access. Plugin, MCP and manual setup.
To run from source:
git clone https://github.com/xplormityai/searchdock-cli.git
cd searchdock-cli npm ci npm run build node dist/cli.cjs --help
Create a Google OAuth Desktop app client in your own Google Cloud project, enable the Search Console API, and download the client JSON. See Google setup for the steps and testing-mode limits. No shared developer credentials are included.
searchdock auth login --client-file /path/to/desktop-client.json
searchdock sites list searchdock sites use sc-domain:example.com searchdock auth status
Google opens a local browser consent flow. SearchDock uses PKCE, validates the callback state, and listens only on 127.0.0.1. It requests webmasters.readonly and keeps the refresh token in your operating system's per-user configuration directory, outside this repository. Credentials are stored as permission-protected local JSON, not encrypted by SearchDock. See privacy.
# Search performance and top queries
searchdock analytics --days 28 searchdock analytics --dimensions page --days 28 --json searchdock analytics --dimensions date --start 2026-09-01 --end 2026-09-30
searchdock analytics --brand "Your Brand" --json
searchdock sitemaps searchdock inspect https://example.com/
searchdock report --urls https://example.com/,https://example.com/about --json searchdock report --output ./private-report.json
searchdock auth login --client-file /path/to/client.json --profile work searchdock sites use https://example.com/ --profile work searchdock analytics --profile work --site https://example.com/ --json
searchdock doctor searchdock auth logout
--json writes machine-readable results to stdout and errors to stderr with a nonzero exit status. --output saves JSON to a new file and refuses to overwrite an existing one. Keep private reports out of Git yourself. CSV is not yet supported. For URLs containing commas, use the MCP urls array or the JavaScript API for batch inspection.
Report windows default to 28 days ending three days before today in Pacific Time, to allow for Search Console processing. You can specify exact dates. Finalized data may still lag. Pagination supports up to 100,000 requested rows, but Google's API returns top rows and omits some anonymized query data. Missing rows do not prove zero demand; zero impressions make average position meaningless.
SearchDock provides five read-only MCP tools: searchdock_sites, searchdock_analytics, searchdock_sitemaps, searchdock_inspect, and searchdock_report. Authenticate locally first; MCP tools do not start consent or change account settings.
Add this stdio server to any compatible MCP client:
{
"mcpServers": { "searchdock": { "command": "npx", "args": ["--yes", "searchdock-cli@0.1.3", "mcp"] } } }
For a source checkout, set command to node and args to ["/absolute/path/searchdock-cli/dist/cli.cjs", "mcp"]. Windows clients that launch npx.cmd through a shell may need command: "cmd" and args: ["/c", "npx", "--yes", "searchdock-cli@0.1.3", "mcp"]. Use your client's Windows configuration guidance.
Plugins use the same pinned npm version:
# Codex CLI
codex plugin marketplace add xplormityai/searchdock-cli codex plugin add searchdock@searchdock
In Claude Code:
/plugin install searchdock --marketplace xplormityai/searchdock-cli --scope project
This one-step command requires Claude Code 2.1.275+. Earlier versions can use /plugin marketplace add xplormityai/searchdock-cli, then /plugin install searchdock@searchdock --scope project.
For standalone skills, copy both skills/searchdock and skills/searchdock-setup into your agent's skills directory. Codex uses ~/.agents/skills/; Claude Code uses ~/.claude/skills/. Install the CLI separately. Both skills are included in the plugin. The repository includes portable Agent Plugins, Codex and Claude manifests; local stdio plugins are not automatically listed in hosted plugin directories.
You can also install the skill with the open skills installer:
npx --yes skills add xplormityai/searchdock-cli --skill searchdock-setup searchdock --agent codex --copy --yes
SearchDock is published in the official MCP Registry under io.github.xplormityai/searchdock-cli. Release workflows update its metadata using GitHub OIDC.
Both SearchDock and setup skills are published on ClawHub. Its skill copies use MIT-0, as required by that registry; this repository and its packages remain MIT licensed.
The local MCPB bundle is published on Smithery. It requires Node.js 22+ and a locally authenticated Google profile; it includes no credentials. python scripts/build_mcpb.py packages a built dist/cli.cjs. Release and discovery automation.
| Available | Requires Search Console UI or an export |
|---|---|
| Clicks, impressions, CTR, average position | Request indexing |
| Top queries/pages and date/device/country breakdowns | Test a live URL |
| Exact brand-query performance | Full Page indexing exclusions table |
| Sitemap processing status | Manual actions and security issues |
| Google's indexed version of specific URLs | Guaranteed current ranking or indexing |
SearchDock's report flags returned sitemap errors/warnings, pending processing and non-PASS verdicts for the URLs you inspect. It is not a complete technical SEO audit, and it does not provide invented SEO/AEO/GEO scores.
import { selectedContext } from 'searchdock-cli';
const { adapter, site } = await selectedContext({ profile: 'default' }); const result = await adapter.analytics(site, { days: 28, dimensions: ['page'] }); console.log(result.rows);
The provider registry declares capabilities separately. Bing can be added as an adapter without changing the CLI, MCP or Python distribution model. Provider-specific differences must remain explicit. See architecture.
npm ci
npm run build npm test npm run check python -m pip install build twine npm run release:artifacts python -m twine check dist/releases/searchdock_cli-0.1.3-py3-none-any.whl dist/releases/searchdock_cli-0.1.3.tar.gz
Release instructions cover npm/PyPI accounts, OIDC trusted publishing, versioning and GitHub release artifacts. Package creation alone does not publish anything.
Built by Xplormity Collective. MIT license.