MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.
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.
CAPX_CHOKEPOINT_URL, CAPX_EMAIL, CAPX_LANE, X_CLIENT_IDYou 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": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add capx-cafe --env CAPX_CHOKEPOINT_URL=your-value --env CAPX_EMAIL=your-value --env CAPX_LANE=your-value --env X_CLIENT_ID=your-value -- npx -y capx-cafeFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capx-cafe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "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 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.
CAPX_LANE envX_CLIENT_ID envThese 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 7, 2026
The registry name was verified with the GitHub account vb-tyagi, 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.
You need to fill in: CAPX_CHOKEPOINT_URL, CAPX_EMAIL
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 2 months 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.
One MCP server. Your X token never touches the agent — and every post clears an enforced guardrail before it ships.
*The guardrail, live — every verdict above is produced by the real chokepoint code (pnpm demo replays it).*
capx café is an agent-native X poster that installs as one MCP server into any coding agent (Claude Code /
Cursor / Codex / Windsurf). A whitelisted user connects their X account once; after that they create /
schedule / post from inside their agent session. The whole product rests on one security thesis: the X
token, the guardrail (casserole), and the send are one inseparable server-side unit — the agent on
your laptop only ever holds a short-TTL session handle, never the token. That's why it structurally can't be
prompt-injected into tweeting a scam. "The AI writes; casserole decides what ships."
Every other "let your AI post" tool has the same flaw: to let an agent post, you paste your X token into a plaintext config right next to an autonomous agent that reads untrusted web pages, issues, and code. One prompt-injection and your account tweets a scam. capx café is the only one that structurally can't be.
→ Full threat model, architecture & the "what we can/can't see" table: [docs/SECURITY.md](docs/SECURITY.md)
flowchart LR
subgraph M["🖥️ your machine · untrusted"] A["agent model writes the draft"] S["capx skills"] C["capx MCP client holds a session handle · NO token"] end subgraph K["🔒 capx chokepoint · hosted · AGPL-3.0"] AD["admission allowlist · kill-switch"] CAS["casserole 6-layer guardrail"] V["vault the token lives here"] XA["x-adapter the only egress"] end X["🐦 X · /2/tweets"] A --> C S --> C C -->|"short-TTL handle crosses — never the token"| AD AD --> CAS CAS -->|PASS| V --> XA --> X CAS -.->|blocked / held| C
The token, the guardrail, and the send live together behind a trust boundary; your agent can only *ask*.
Six deterministic layers on every post. Worst result wins — pass / rewrite / hold / block — and a blocked post never even decrypts the token.
flowchart TD
D["draft"] --> AD{"admitted? allowlisted · not killed"} AD -->|no| R["rejected"] AD -->|yes| CAS["casserole L1 eligibility · L2 rate · L3 anti-slop L4 authenticity · L5 kill-switch · L6 audit"] CAS --> VER{"verdict"} VER -->|block| B["blocked — never sent 🔒 token never decrypted"] VER -->|hold| H["held for your review"] VER -->|rewrite| RW["ask the agent to fix"] VER -->|pass| SEND["vault → x-adapter → X ✅"]
npx -y capx-cafe # runs the MCP server — add it to your agent's MCP config
Then, inside your agent:
"connect my X account" → opens a browser once; the token stays on the server
"post: shipping the thing today" → clears casserole, or tells you exactly why not "turn my last week of commits into a build-in-public thread" → drafts + queues it
Set CAPX_EMAIL (your whitelisted email) and, for the BYO lane, X_CLIENT_ID (your own X app) in ~/.capx/config.json or your agent's MCP env. A guided setup page hands you the exact callback URL to paste.
| Agent | How |
|---|---|
| Claude Code | /plugin marketplace add vb-tyagi/capx-cafe → /plugin install capx-cafe (MCP + slash commands + skills) |
| Cursor | add to .cursor/mcp.json; skill rules in plugins/capx-cafe/adapters/cursor/ |
| Codex | add to your MCP config; prompt pack in plugins/capx-cafe/adapters/codex/ |
| Windsurf | add to MCP config; workflows in plugins/capx-cafe/adapters/windsurf/ |
| Any MCP agent | point it at npx -y capx-cafe |
| Docker Desktop | docker mcp catalog pull ghcr.io/vb-tyagi/capx-catalog:latest → MCP Toolkit → enable capx café |
| Tool | What it does |
|---|---|
connect_x | One-time browser OAuth — the token lands in the server vault, never on your machine |
post_now | Post now (clears casserole first). Supports reply-chains and media |
preview | Dry-run a draft through the guardrail without sending — pass / hold / block + why |
audit | The durable record of what capx posted or attempted on your behalf, and its state |
create_loop · list_loops · … | Scheduled posting — a queue you wrote, sent on a schedule, laptop-off |
upload_media | Stream a local image/video to X and attach it (media you made with your own tools) |
whoami | The connected account + its status |
capx lives inside a *coding* agent, so it has what no social scheduler does: your repo, commits, PRs, releases. Skills turn that into posts — automatically, and always through the guardrail.
flowchart LR
G["git commits"] --> BIP["build-in-public drafts a week of posts"] BIP --> Q["loop queue"] Q -->|"1/day · laptop-off"| POST["posted to X"] Q -.->|"runs low"| GAP["gap-alert"] GAP -.->|"top up from new commits"| BIP
The self-refilling content engine: you code → commits accrue → the loop drains as it posts → gap-alert tops it up from the *new* commits. Your normal work *is* the pipeline.
image-director, video-director, prompt-engine, model-guide: capx runs no models; it guides *your* image/video tools (higgsfield, fal, kling, …) and uploads the result. casserole guards your caption; you own the media.*One canonical SKILL.md per skill, generated for all four agents. capx never writes the content — it makes good content easy and stops bad content regardless of which skill produced it.*
Short $5 / Tall $15 / Grande $35 monthly tiers + top-up packs, quotas enforced server-side at the gate. Full sheet + the math: [docs/ECONOMICS.md](docs/ECONOMICS.md) · policy posture: docs/X-COMPLIANCE.md.The chokepoint is open source (AGPL-3.0). Run the identical image with your own X app, keys, database, and domain — CAPX_DEPLOY_MODE=self-host, zero telemetry to capx. See the self-host-guide skill and docs/HANDOFF.md.
MIT for the client and everything it bundles (apps/capx-mcp, core, config, platform-client) plus skills & docs. AGPL-3.0 for the server half (the chokepoint + casserole/captain/counter/canteen/ chef). Full map: [LICENSING.md](LICENSING.md).
Private alpha, whitelist-only. The first real post shipped 2026-07-19 — guardrail-cleared, token never on the machine. Not yet open for public signups.
Node ≥ 22.6 (TypeScript runs natively via --experimental-strip-types — no build step). pnpm run verify = unit tests across packages / services / apps + tsc. Contributions accepted under the project CLA.
capx café · security · architecture · license