MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Research X (Twitter), read inboxes and review publishing through MCP. No X API key required.
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.
X_USE_HOME, OPENAI_API_KEY, OPENAI_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"x-use": {
"command": "uvx",
"args": [
"x-use-mcp"
],
"env": {
"X_USE_HOME": "your-value",
"OPENAI_API_KEY": "your-value",
"OPENAI_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add x-use --env X_USE_HOME=your-value --env OPENAI_API_KEY=your-value --env OPENAI_BASE_URL=your-value -- uvx x-use-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"x-use": {
"command": "uvx",
"args": [
"x-use-mcp"
],
"env": {
"X_USE_HOME": "your-value",
"OPENAI_API_KEY": "your-value",
"OPENAI_BASE_URL": "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": {
"x-use": {
"type": "stdio",
"command": "uvx",
"args": [
"x-use-mcp"
],
"env": {
"X_USE_HOME": "your-value",
"OPENAI_API_KEY": "your-value",
"OPENAI_BASE_URL": "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.
X_USE_HOME envOPENAI_BASE_URL 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 8, 2026
The registry name was verified with the GitHub account ihuzaifashoukat, 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: OPENAI_API_KEY
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 (3.2.0) reached the registry 25 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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.
Connect your AI client to X research, inbox reads, and reviewed publishing.
x-use is an open-source Python Model Context Protocol (MCP) server and CLI for X (Twitter). Connect Claude, Codex, Cursor or another local MCP client to profile research, inbox management and reviewed publishing. It uses your authenticated browser session, supports multiple accounts and runs locally without official X API credentials.
Quickstart · Documentation · Tool reference · Discussions · Contribute
Your AI client supplies the reasoning and text. An optional OpenAI-compatible LLM configuration supports server-side generation; ordinary explicit-text MCP workflows do not need that extra key.
Requires Python 3.11+ and Chromium. The CI matrix covers Python 3.11–3.14 on Windows, macOS and Linux.
Version 3.2.0 provides 82 tools for research, inbox management, reviewed publishing and account operations. Upgrade the package and restart your MCP client to load the current tools.
python -m pip install --upgrade x-use-mcp
python -m patchright install chromium
Windows PowerShell:
$env:X_USE_HOME = "$env:LOCALAPPDATA\x-use"
x-use init x-use doctor
macOS / Linux:
export X_USE_HOME="$HOME/.local/share/x-use"
x-use init x-use doctor
The wizard configures your account and imports your own X session cookies from a local JSON export. Keep cookies and inbox PINs private. Use the same absolute data directory in your client configuration below; shell environment settings alone do not configure a desktop client.
Use this stdio configuration in clients that accept an mcpServers object, such as Claude Desktop:
{
"mcpServers": { "x-use": { "command": "/absolute/path/to/x-use", "args": ["mcp"], "env": { "X_USE_HOME": "/absolute/path/to/x-use-data" } } } }
Replace both paths. On Windows, use the installed x-use.exe path and forward slashes in JSON, for example C:/Users/you/AppData/Local/x-use for the data directory. Locate the executable with Get-Command x-use in PowerShell or command -v x-use on macOS/Linux.
Claude Code, Codex, Cursor and Windsurf have their own registration locations or commands. Follow the client setup instructions, then reload the client if required. Ask it to call list_accounts before starting browser work.
With draft mode enabled, ask your client:
Check my account health, research the profile I specify, and summarize its recent visible posts. Prepare one relevant reply draft and show me its ID and exact text. Wait for my approval before publishing.
The flow is get_account_health → get_profile_context → prepare_reply → reply_to_tweet → get_draft. The reply tool stages a draft under the default policy; prepare_reply supplies context. Use approve_draft only when authorized.
More workflow examples cover inbox triage, outreach and threads.
Install from source or let your agent handle setup
git clone https://github.com/ihuzaifashoukat/x-use.git
cd x-use python scripts/setup_uv.py --dev
On Windows you can use py -3 scripts/setup_uv.py --dev; on macOS/Linux use python3 if needed. Setup installs uv when missing, synchronizes locked dependencies into .venv, installs matching Chromium, creates missing sample configuration and runs diagnostics. Activate the environment or use its executable directly. Then initialize your account.
For assisted installation, use the setup prompt or install the root setup skill:
npx skills add ihuzaifashoukat/x-use
The Claude Code plugin includes the bundled skills and MCP configuration guidance.
| Workflow | Representative tools | Details |
|---|---|---|
| Profile and post research | get_profile_context, search_profile, search_tweets, get_tweet, get_thread | Visible profile, post, media and bounded thread evidence |
| Inbox and notifications | get_inbox, search_conversations, get_conversation, get_notifications | Inbox/request folders, read-state evidence and partial message history |
| Publishing and inbox controls (3.1.0) | get_bookmarks, edit_tweet, delete_tweet, unfollow_profile, manage_conversation | Reviewed changes; supported controls and limitations |
| Reviewed publishing | post_tweet, reply_to_tweet, prepare_thread, approve_draft | Persistent drafts and resumable thread progress |
| Individual outreach | prepare_outreach, send_message, follow_profile | Message and follow drafts require individual approval |
| Leads and campaigns | upsert_lead, create_campaign, prepare_campaign_messages, opt_out_lead | Local records, suppression and bounded batches |
| Account readiness (3.1.0) | get_account_health, get_session_status, test_proxy | Operational score, evidence and recovery advice, plus explicit proxy connectivity checks |
| Scheduling and recovery | queue_post, process_queue, get_account_health, resolve_action_outcome | Durable budgets, explicit recovery and uncertain-outcome tracking |
Version 3.2.0 includes 82 tools, seven prompts, four resource patterns and seven bundled skills. 3.1.0 added runtime diagnostics, campaign previews, bookmarks, reviewed post edits/deletions, engagement reversal and inbox controls to the 70 tools in 3.0.0; 3.2.0 keeps the same tools on the MCP Python SDK v2 line. See publishing and inbox controls for supported layouts and testing limits.
The MCP guide documents every tool, prompt and resource. Validation evidence separates local protocol checks, synthetic browser fixtures and authorized live-account checks.
For a uvx client, use uvx x-use-mcp or pin the release with uvx x-use-mcp==3.2.0. The x-use-mcp executable starts MCP without arguments; the existing x-use mcp command remains supported. Clients pinned to 3.0.0 must use uvx --from x-use-mcp==3.0.0 x-use mcp.
The current MCP runtime uses async Patchright Chromium with separate account contexts. Your configuration, cookies, drafts, queue and action journals live under X_USE_HOME. AI-client and optional model-provider data handling depends on the client and provider you choose.
The protocol implementation uses the MCP Python SDK v2 line (mcp>=2.3,<3). It negotiates handshake protocol versions 2024-11-05 through 2025-11-25 with existing clients.
Draft mode is enabled by default for ordinary publishing. Messages, follows and thread starts require draft approval. Direct publishing mode, explicit queue processing, opt-in auto-drain and the legacy batch runner have separate execution paths. Review the configuration reference before changing these settings.
The development checkout allows one MCP server process per X_USE_HOME, preventing concurrent servers from using stale draft and queue state. Close the existing connection before opening the same data directory in another client.
x-use run / run_cycle) executes separately from MCP draft review. Community posting is not currently verified in the async runtime.See browser behavior and recovery and responsible-use guidance.
No. It operates visible X pages through a browser authenticated with your session cookies. It does not require official X API credentials. Optional server-side text generation may require an LLM provider key.
Clients that launch local stdio MCP servers can use x-use. Setup examples cover Claude Desktop, Claude Code, Codex, Cursor and Windsurf. Client-specific discovery and reload behavior varies.
No. Message drafts require individual approval. Other write behavior depends on draft mode, queue execution and the legacy runner; check the configured policy before requesting actions.
Yes. Accounts have separate cookies, browser contexts and policy settings, with optional proxy routes. Browser capacity is bounded and depends on your host and configuration.
Version 3.1.0 added reviewed edits and deletion of your own posts, bookmarks, unfollowing, and supported conversation request, mute/unmute and deletion actions. X determines edit eligibility. Inbox history is partial, and per-message editing/deletion, attachment sending a
Only the beginning is shown; read the rest in the repo