InsightSocial vs YouTube
A side-by-side look at the InsightSocial and YouTube MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose InsightSocial for social media work as a local process; choose YouTube 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 InsightSocial when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INSIGHTSOCIAL_API_KEY, INSIGHTSOCIAL_BASE_URL, INSIGHTSOCIAL_HOME.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 44/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | INSIGHTSOCIAL_API_KEYINSIGHTSOCIAL_BASE_URLINSIGHTSOCIAL_HOME | API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,822 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View InsightSocial | View YouTube |
Tools & capabilities
InsightSocial tools
No tool names declared yet. Check the project README from the listing page.
YouTube 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.
InsightSocial
{
"mcpServers": {
"insightsocial": {
"command": "npx",
"args": [
"-y",
"insightsocial"
],
"env": {
"INSIGHTSOCIAL_API_KEY": "YOUR_INSIGHTSOCIAL_API_KEY_HERE",
"INSIGHTSOCIAL_BASE_URL": "YOUR_INSIGHTSOCIAL_BASE_URL_HERE",
"INSIGHTSOCIAL_HOME": "YOUR_INSIGHTSOCIAL_HOME_HERE"
}
}
}
}
YouTube
{
"mcpServers": {
"klavis-ai-youtube": {
"command": "uvx",
"args": [
"klavis"
],
"env": {
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
InsightSocial is categorized under Social Media and uses a local stdio subprocess. YouTube belongs to Social Media and uses a local stdio subprocess. Pick InsightSocial for social media work and YouTube 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.
InsightSocial has no declared pricing — check the project's own site. YouTube is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 insightsocial and klavis-ai-youtube as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, InsightSocial has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. YouTube has 49/100 (Fair) with 4 views, 0 installs and 5,822 GitHub stars.