| FMRS | 41 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 7 / 20 | 10 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 |
|---|
| Maintenance | 7 / 20 | 18 / 20 |
|---|
| Documentation | 9 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 14 / 20 |
|---|
| Best for | - Marketers managing Facebook and Instagram advertising
- Teams wanting conversational AI analysis and control of Meta Ads
- Users who prefer hosted remote MCP access without managing infrastructure
- Users needing dynamic creative testing and performance insights
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users who only need read-only reporting and do not want write access
- Users without Meta advertising activity or an accessible ad account
- Users requiring fully self-hosted operation with no hosted service
- Users specifically seeking an MCP server maintained by Meta
| - Users needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| Required permissions | - Requires access to Meta ad accounts, campaigns, ad sets, ads, creatives, Pages, and performance data depending on the tool used
- Write operations may create or modify campaigns, ad sets, ads, creatives, budgets, statuses, and targeting
- Authentication uses Pipeboard OAuth or a Pipeboard token; local deployment requires a Meta Developer App
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| Risks and side effects | - Creating or updating ads can trigger real delivery and spending; writes should be reviewed before confirmation
- Incorrect budgets, bids, targeting, or statuses can affect performance and spend
- The remote service processes ad-account requests; users should evaluate their trust in Pipeboard
- Image uploads and creative changes can affect brand presentation and campaign results
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude, Claude Desktop, ChatGPT, Perplexity, Cursor, Cherry Studio | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 29 | 11 |
|---|