Ext Ops Panel
Open dashboard
Comparison

Planify vs Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

Planify is an MCP server published by planifyapps.com. Marketplaces we read that list it: 1 (Official MCP Registry). Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads is an MCP server published by adkit. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePlanifyAds Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 403
Downloads/week (npm): 53
Not marked · First seen
Listed
Version: 1.0.6
Forks (GitHub): 2
Stars (GitHub): 15
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Planify vs Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads
FactPlanifyAds Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub15
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@planifyapps/mcp)Remote server (mcp.adkit.so)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle4
Licence (differs)Not statedMIT
Repository (differs)github.com/gsrathoreniks/planifywebgithub.com/adkit/ads-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Planify

In its own words, on Official MCP Registry:

Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.

Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

In its own words, on Official MCP Registry:

PPC advertising on Google Ads, Meta Ads (Facebook Ads), TikTok Ads, LinkedIn Ads, Reddit Ads & more.

How to run each

Planify As a local MCP server: npm package

Claude Code
claude mcp add --env "PLANIFY_API_KEY=<YOUR_PLANIFY_API_KEY>" --transport stdio planify -- npx -y @planifyapps/mcp

Requires: PLANIFY_API_KEY (secret)

Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads As a remote MCP server

Claude Code
claude mcp add --transport http ads https://mcp.adkit.so

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads publish no settings it asks for, so we do not compare settings.

What it can do: Planify · What it can do: Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built