clay vs Planify
clay is a plugin bundle for AI coding tools published by clay-run. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). Planify is an MCP server published by planifyapps.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 2.26.0 Forks (GitHub): 22 Stars (GitHub): 134 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 No figure published 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
| Fact | clay | Planify |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 134 | No figure on GitHub |
| Forks (GitHub) (differs) | 22 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@planifyapps/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 37 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/clay-run/agent-plugins | github.com/gsrathoreniks/planifyweb |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
clay
Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.
Planify
Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.
How to run each
clay As a Claude Code plugin
/plugin install clay@claude-plugins-officialPlanify As a local MCP server: npm package
claude mcp add --env "PLANIFY_API_KEY=<YOUR_PLANIFY_API_KEY>" --transport stdio planify -- npx -y @planifyapps/mcpRequires: PLANIFY_API_KEY (secret)
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 clay publish no settings it asks for, so we do not compare settings.
What it can do: clay · What it can do: Planify · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.