YouTube vs Post Bridge
A side-by-side look at the YouTube and Post Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose YouTube for social media work as a local process; choose Post Bridge for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose YouTube when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_KEY.
Choose Post Bridge when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_social_accounts, create_post, update_post.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 44/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,823 | 17 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View YouTube | View Post Bridge |
Tools & capabilities
YouTube tools
No tool names declared yet. Check the project README from the listing page.
Post Bridge tools 14
list_social_accountscreate_postupdate_postget_postlist_postsdelete_postlist_post_resultsupload_mediarequest_upload_linklist_mediadelete_medialist_analytics- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
YouTube
{
"mcpServers": {
"klavis-ai-youtube": {
"command": "uvx",
"args": [
"klavis"
],
"env": {
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
Post Bridge
{
"mcpServers": {
"post-bridge": {
"command": "npx",
"args": [
"-y",
"postbridge-cli"
]
}
}
}
Frequently asked questions
YouTube is categorized under Social Media and uses a local stdio subprocess. Post Bridge belongs to Social Media and uses a local stdio subprocess. Pick YouTube for social media work and Post Bridge for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
YouTube is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Post Bridge has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add klavis-ai-youtube and post-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, YouTube has a quality signal of 44/100 (Fair) with 4 views, 0 installs and 5,823 GitHub stars. Post Bridge has 56/100 (Good) with 0 views, 0 installs and 17 GitHub stars.