A side-by-side look at the Postbase and Video URL Analyzer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postbase for social media work as a local process; choose Video URL Analyzer 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?
P
Choose Postbase when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
Video URL Analyzer tools
No tool names declared yet. Check the project README from 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.
Postbase is categorized under Social Media and uses a local stdio subprocess. Video URL Analyzer belongs to Social Media and uses a local stdio subprocess. Pick Postbase for social media work and Video URL Analyzer 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.
Postbase has no declared pricing — check the project's own site. Video URL Analyzer 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 postbase and video-url-analyzer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Postbase has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Video URL Analyzer has 37/100 (Fair) with 1 views, 0 installs and 3 GitHub stars.