A side-by-side look at the MCP Meta Ad Library Monitor and Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Meta Ad Library Monitor for social media work as a local process; choose Agent for social media as a local process. You can also run both side by side in one mcpServers block.
APIFY_TOKEN, META_ACCESS_TOKEN.TAISLY_API_KEY.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 | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | APIFY_TOKENMETA_ACCESS_TOKEN | TAISLY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 219 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Meta Ad Library Monitor | View Agent |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"mcp-meta-ad-library-monitor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-meta-ad-library-monitor"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE",
"META_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"taisly-agent": {
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "YOUR_TAISLY_API_KEY_HERE"
}
}
}
}