kadenzo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KADENZO_API_KEY | Yes | Your Kadenzo API key (e.g., kdz_live_xxxxxxxxxxxxxxxxxxxxxxxx) | |
| KADENZO_API_BASE | No | Override the API base URL | https://studio.kadenzo.app/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List the social accounts connected to this Kadenzo workspace — returns each account id, platform, and username. Use the ids as account_ids when scheduling. |
| schedule_postA | 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. |
| list_postsA | List your posts, newest first. Optionally filter by status (comma-separated, e.g. "pending,posted") and paginate with limit (1-100) and offset. |
| get_postA | Get one post: roll-up status, per-channel outcome, and any options/thread that were set on it. |
| update_postA | Edit a post that has not published yet — change content, accounts, time, media, options, or thread. |
| cancel_postB | Cancel a scheduled post before it publishes. Already-published posts cannot be cancelled. |
| upload_mediaA | Upload a local image or video file and get a hosted URL to use in media_urls when scheduling. |
| get_account_analyticsC | Recent posts and their engagement metrics for one connected account (likes, comments, views, etc.). The reliable analytics surface. |
| get_post_analyticsA | Per-channel engagement metrics for a specific post you scheduled (best-effort; use get_account_analytics for the full picture). |
| generate_contentA | Generate post copy for a platform from a topic — great for a "generate then schedule" flow. Returns a caption/post/description you can feed into schedule_post. Platform must be one of: instagram, tiktok, snapchat, facebook, youtube. |
| get_best_timesA | 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. |
| list_mentionsB | 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. |
| post_commentA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct action—content generation, scheduling, analytics, listening, and engagement—with no functional overlap. Even similar tools like get_account_analytics and get_post_analytics are clearly differentiated by scope and usage guidance.
All tool names follow a consistent verb_noun snake_case pattern (e.g., generate_content, list_accounts, post_comment). Verbs like get/list are appropriately used for singles vs. multiples, and the pattern is uniform across all 13 tools.
13 tools cover the full social media scheduling lifecycle—content creation, media upload, scheduling, updates, cancellation, analytics, and social listening—without redundancy. The count feels well-scoped for a server of this purpose.
Core workflows (schedule, update, cancel, analytics) are fully covered. Minor gaps exist (e.g., no media deletion or account creation), but they are not essential for the primary scheduling use case and would likely fall outside the server's intended scope.