Dynamoi vs Meta Ads MCP

A side-by-side look at the Dynamoi and Meta Ads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dynamoi logoDynamoiMarketing · Remote HTTP/SSEPromote music on Spotify and grow YouTube channels through AI-powered Meta and Google ad campaigns.60GoodAuth: oauth 2.0Meta Ads MCP logoMeta Ads MCPMarketing · Local subprocess (stdio)MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.68GreatAuth: api key required

Verdict: choose Dynamoi for marketing work over a hosted endpoint; choose Meta Ads MCP for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dynamoi logoChoose Dynamoi when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like dynamoi_open_workspace, dynamoi_about, dynamoi_get_account_overview.
Explore Dynamoi

Meta Ads MCP logoChoose Meta Ads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: META_ADS_ACCESS_TOKEN, META_AD_ACCOUNT_ID.
  • You want tools like list_campaigns, get_campaign, create_campaign.
Explore Meta Ads MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDynamoi logoDynamoiMeta Ads MCP logoMeta Ads MCP
CategoryMarketingMarketing
Quality signal60/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0API key required
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedMETA_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID
Verified ownerCommunity listingCommunity listing
GitHub stars391
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools24134

Tools & capabilities

Dynamoi tools 24

  • dynamoi_open_workspaceOpen the read-only Dynamoi workspace when the user wants to browse their existing artists, campaigns, Smart Links and observed results in ChatGPT. Returns an authorized artist roster or an honest empty account state. Does not create links, change campaigns, start purchases or connect accounts. Use individual read tools for follow-up details.
  • dynamoi_aboutUse this when the user asks what Dynamoi is, who it is for, or what it offers — including before sign-in or before choosing a tool. Returns the canonical About Dynamoi text plus a short structured summary covering free Smart Links, managed Smart Campaigns, YouTube campaigns, distribution, company facts, support, and getting started. This is read-only product information, not account data.
  • dynamoi_get_account_overviewUse this when the user explicitly asks about the signed-in Dynamoi account itself, such as who is logged in, how many organizations or artists it can access, or whether account-level platform connections exist. Pass intent to match that explicit account question; it defaults to account_overview. Do not use this to confirm a specific Meta or YouTube onboarding attempt because this account-level state can span multiple artists; use dynamoi_get_platform_status for the target artist instead. Do not use this to enumerate artists one by one; use dynamoi_list_artists for that. Never use this to 'check context' before answering generic Instagram, lyrics, songwriting, or marketing-advice questions, even if Dynamoi is attached.
  • dynamoi_list_artistsUse this when the user wants to see which artists or YouTube channels they manage, along with billing status, active campaign count, and their role. Pass artistId when you need the full profile/readiness details for one artist instead of a roster page. Do not use this for campaign details; use dynamoi_list_campaigns or dynamoi_get_campaign. Never use this for generic social-media or marketing advice, including Instagram follower-growth questions, unless the user explicitly asked about their Dynamoi roster. If the result is empty, the user is brand-new — do not stop with 'no records found'; route through dynamoi_get_account_overview.recommendedNextActions.
  • dynamoi_searchUse this when the user mentions an artist, release, campaign, or smart link but you do not yet know the exact record to inspect. Do not use this for analytics summaries or billing questions once you already know the target record. If the result is empty for a brand-new user (no artists yet), do not respond 'no records found' as a terminal answer — instead suggest creating their first artist hub via dynamoi_create_smart_links_from_spotify_artist.
  • searchOpenAI ChatGPT Deep Research / Connectors search contract. Returns matching Dynamoi artists, campaigns, and Smart Links so they can be cited in a deep-research session. For regular ChatGPT chat use dynamoi_search instead.
  • fetchOpenAI ChatGPT Deep Research / Connectors fetch contract. Given an id returned by `search` (formatted as 'artist:<uuid>', 'campaign:<uuid>', or 'smartlink:<uuid>'), returns the full record for citation.
  • dynamoi_list_campaignsUse this when the user wants to browse campaigns for one artist, optionally filtered by type or status. Do not use this for a single campaign deep dive; use dynamoi_get_campaign for that. Never use this to personalize generic marketing advice. If the user has no artists yet, do not call this — route via dynamoi_get_account_overview first.
  • dynamoi_get_campaignUse this when the user wants full details for one campaign, including budget, targeting, platform status, and next actions. YouTube campaigns return youtubeStrategy and strategyGuide: read the guide's goal and judgeBy before interpreting results. Set includeAnalytics=true for paid delivery, includeChannelResults=true for observed YouTube channel results with paid and organic views (never attributed to the campaign), includeDeploymentStatus=true for delivery/deployment blockers, and includeCountries=true only when the full country list is needed. Do not use this for a campaign list; use dynamoi_list_campaigns instead. After a successful launch or campaign mutation, prefer format=summary when you need a follow-up read to relay the final answer.
  • dynamoi_get_artist_analyticsUse this when the user wants artist-level performance across all campaigns, including 30-day rollups or daily breakdowns. Pass granularity=DAILY when the user asks for a daily breakdown. Pass format=summary when the user wants a written rollup, a strongest-campaign verdict, or a direct answer you can relay immediately. If this tool already returned the requested strongest-campaign comparison, stop and answer instead of calling more analytics tools. For one campaign's metrics, use dynamoi_get_campaign with includeAnalytics=true.
  • dynamoi_get_growth_auditUse this when the user asks for an artist's Spotify monthly listeners, listener growth over time, growth audit or score, playlist reach, or growth recommendations. The response carries its status, coverage dates, and limitations; preserve unavailable or stale status and do not treat a missing metric as zero. This is Spotify and market insight data, not paid campaign performance.
  • dynamoi_get_playlist_analyticsUse this when the user asks about an artist's tracked playlist placements, reach, or playlist movement. The response includes freshness and snapshot dates with the playlist and movement rows. These observed placements are not attributed to a paid campaign.
  • +12 more on the listing page

Meta Ads MCP tools 134

  • list_campaignsList campaigns in the ad account. Supports filtering by status and objective. Returns paginated results.
  • get_campaignGet details of a specific campaign by ID.
  • create_campaignCreate a new ad campaign. Defaults to PAUSED status. Requires name and objective. Budget can be set at campaign or ad set level.
  • update_campaignUpdate an existing campaign. Only provided fields will be modified.
  • delete_campaignDelete a campaign. This action is irreversible.
  • copy_campaignCopy an existing campaign. Creates a duplicate with optional name override. Copies structure including ad sets and ads.
  • get_campaign_adsetsGet all ad sets belonging to a specific campaign.
  • get_campaign_adsGet all ads belonging to a specific campaign.
  • get_campaign_leadsGet leads generated by a specific campaign. Requires leads_retrieval permission.
  • list_adsetsList ad sets in the ad account. Optionally filter by campaign or status.
  • get_adsetGet details of a specific ad set by ID.
  • create_adsetCreate a new ad set. Requires name, campaign_id, budget, optimization_goal, billing_event, and targeting. Defaults to PAUSED status.
  • +122 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.

Dynamoi

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dynamoi": {
      "url": "https://dynamoi.com/mcp"
    }
  }
}

Meta Ads MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mikusnuz-meta-ads-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-ads-mcp"
      ],
      "env": {
        "META_ADS_ACCESS_TOKEN": "YOUR_META_ADS_ACCESS_TOKEN_HERE",
        "META_AD_ACCOUNT_ID": "YOUR_META_AD_ACCOUNT_ID_HERE"
      }
    }
  }
}

Frequently asked questions

Dynamoi is categorized under Marketing and uses a remote HTTP/SSE transport. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Dynamoi for marketing work and Meta Ads MCP for marketing.

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.

Dynamoi has no declared pricing — check the project's own site. Auth: oauth 2.0. Meta Ads MCP 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 dynamoi and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dynamoi has a quality signal of 60/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars.