Ad Copy Ai tools for AI agents. Capabilities: generate ad copy, generate variants, create campaign. Built by MEOK AI Labs.
Kadenzo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
MCP server for Kadenzo — schedule, manage, generate, and analyze social posts across 11 networks from any AI agent (Claude, Cursor, ChatGPT).
Quickstart
# 1 — run it from where its publisher ships it
npx -y kadenzo-mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP server for Kadenzo — schedule, manage, generate, and analyze social posts across 11 networks from any AI agent (Claude, Cursor
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Kadenzo as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add kadenzo-mcp -- npx -y kadenzo-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: KADENZO_API_KEY. You set it after installing; the value is sealed here and sent to the server on each call.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the social accounts connected to this Kadenzo workspace — returns each account id, platform, and username. Use the ids as account_ids when scheduling.
Takes no parameters.
Schedule a social post to one or more connected accounts for a FUTURE time (it publishes automatically). Set validate_only=true to check accounts/limits/timing without scheduling.
Takes no parameters.
List your posts, newest first. Optionally filter by status (comma-separated, e.g.
Takes no parameters.
Get one post: roll-up status, per-channel outcome, and any options/thread that were set on it.
Takes no parameters.
Edit a post that has not published yet — change content, accounts, time, media, options, or thread.
Takes no parameters.
Cancel a scheduled post before it publishes. Already-published posts cannot be cancelled.
Takes no parameters.
Upload a local image or video file and get a hosted URL to use in media_urls when scheduling.
Takes no parameters.
Recent posts and their engagement metrics for one connected account (likes, comments, views, etc.). The reliable analytics surface.
Takes no parameters.
Per-channel engagement metrics for a specific post you scheduled (best-effort; use get_account_analytics for the full picture).
Takes no parameters.
Generate post copy for a platform from a topic — great for a
Takes no parameters.
Personalized best posting times for one connected account, computed from its own engagement history. Requires the Professional plan or higher. Hours are UTC; shift to the poster’s timezone. Use it to pick scheduled_for.
Takes no parameters.
Your social-listening mentions — who is talking about the keywords you track (reddit/bluesky/youtube/hackernews/…), newest first. Filter by platform, since (ISO), or unread.
Takes no parameters.
Post a comment/reply to one of your posts. account_id from list_accounts; target_id is the platform post/media/comment id to comment on. Supported: instagram, facebook, linkedin.
Takes no parameters.
List the social-listening keywords this workspace tracks — id, keyword, role (brand/competitor/topic), platforms, aliases, active state. Mentions for them arrive via list_mentions.
Takes no parameters.
Start tracking a social-listening keyword. Per-plan keyword caps apply (Professional 5, Enterprise 15). Mentions are fetched on the listening pipeline\
Takes no parameters.
Edit a tracked keyword — including is_active=false to pause tracking without losing history.
Takes no parameters.
Stop tracking a keyword and drop its mentions. Prefer update_keyword with is_active=false if the user may want the history back.
Takes no parameters.
Aggregated social-listening analytics: mention volume over time, per-platform split, sentiment distribution and trend, totals. Defaults to quality-filtered mentions.
Takes no parameters.
Share of Voice report — your brand keywords vs competitor keywords: per-keyword mention/sentiment totals, your share of relevant conversation (current + previous window), daily series. Requires the Enterprise plan (403 otherwise — do not retry).
Takes no parameters.
List the DM automation rules on your Instagram/Facebook accounts, with per-rule funnel stats (reached → opted in → clicked, plus captured emails), this month\
Takes no parameters.
Create a DM automation rule. trigger_type: comment_keyword (comment → DM; REQUIRES opening_message + button_label — Meta\
Takes no parameters.
Edit a DM automation rule — most commonly active=false/true to pause or resume it. comment_keyword rules cannot drop opening_message or button_label.
Takes no parameters.
Delete a DM automation rule permanently. Prefer update_dm_automation with active=false if the user may want it back.
Takes no parameters.
- 25,000 calls a month, included
- 300 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
- 200,000 calls a month, included
- 2,400 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $29 a month covers every tool at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_accounts | no tags | |
| schedule_post | no tags | |
| list_posts | no tags | |
| get_post | no tags | |
| update_post | no tags | |
| cancel_post | no tags | |
| upload_media | no tags | |
| get_account_analytics | no tags | |
| get_post_analytics | no tags | |
| generate_content | no tags | |
| get_best_times | no tags | |
| list_mentions | no tags | |
| post_comment | no tags | |
| list_keywords | no tags | |
| add_keyword | untrusted-input | |
| update_keyword | no tags | |
| delete_keyword | no tags | |
| get_listening_analytics | no tags | |
| get_share_of_voice | no tags | |
| list_dm_automations | no tags | |
| create_dm_automation | no tags | |
| update_dm_automation | no tags | |
| delete_dm_automation | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.4.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Kadenzo in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.