InsightSocial vs Meta Ads
A side-by-side look at the InsightSocial and Meta Ads 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 Meta Ads 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 Meta Ads when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
META_ACCESS_TOKEN. - You want tools like
meta_health_check, meta_get_business_assets, meta_get_pages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 44/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | INSIGHTSOCIAL_API_KEYINSIGHTSOCIAL_BASE_URLINSIGHTSOCIAL_HOME | META_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 41 |
| Full listing | View InsightSocial | View Meta Ads |
Tools & capabilities
InsightSocial tools
No tool names declared yet. Check the project README from the listing page.
Meta Ads tools 41
meta_health_checkAgent-ready read-only health check: validates token metadata, lists accessible ad accounts, and warns about missing read scopes without exposing the access token.meta_get_business_assetsDiscover accessible Meta Business assets read-only: businesses, pages, Instagram accounts, pixels, and datasets when permissions allow.meta_get_pagesList accessible Facebook Pages with id, name, category, tasks, picture, and linked Instagram account references when available.meta_get_instagram_accountsList Instagram accounts linked to accessible Pages, Business Manager assets, or an ad account when permissions allow.meta_get_pixelsList pixels and datasets from an ad account or Business Manager when accessible, returning actionable warnings for permission-limited edges.meta_get_ad_activityRead ad account activity logs from /{ad_account_id}/activities with object, event, actor, timestamp, and extra_data fields.meta_get_delivery_diagnosticsAggregate read-only delivery diagnostics across campaigns, ad sets, and ads using status/effective_status/issues_info where available plus simple delivery insights.meta_get_creative_assetsReturn ad-linked creative media with actual ad names, collection covers, all carousel/flexible components, resolved image hashes and video URLs. Catalog-only ads are classified separately; use the hosted GetMCPAds service for an interactive visual gallery. Raw creative metadata remains available for diagnostics.meta_get_audience_detailsRead detailed custom, saved, and lookalike audiences with pagination and rich fields where permissions allow.meta_get_catalog_productsRead Product Catalogs and Product Items when catalog access is available. Returns join-ready product metadata without creating or updating catalog assets.meta_join_product_insightsQuery product-breakdown insights and enrich rows with Product Catalog metadata when catalog access is available.meta_get_brand_safety_controlsRead brand safety, suitability, placement, and context-control signals from ad account/ad set targeting and optional block-list edges.- +29 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.
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"
}
}
}
}
Meta Ads
{
"mcpServers": {
"meta-ads": {
"command": "npx",
"args": [
"-y",
"@getmcpads/meta-ads-mcp-server"
],
"env": {
"META_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN_HERE"
}
}
}
}
Frequently asked questions
InsightSocial is categorized under Social Media and uses a local stdio subprocess. Meta Ads belongs to Social Media and uses a local stdio subprocess. Pick InsightSocial for social media work and Meta Ads 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. Meta Ads 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 insightsocial and meta-ads 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. Meta Ads has 61/100 (Good) with 4 views, 0 installs and 1 GitHub stars.