Skip to main content
Glama
Kadenzo

kadenzo-mcp

by Kadenzo

Related Servers

Alternatives to kadenzo-mcp

  • A
    license
    A
    quality
    A
    maintenance
    Gives AI agents the ability to schedule and publish social media posts to Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Pinterest, Threads, and Bluesky. Create, schedule, and bulk-plan posts with per-platform captions, then check per-platform results and retry failures.
    12
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Social media scheduling and publishing for AI agents. 17 validation-first tools to post to X, LinkedIn, Instagram, TikTok, YouTube, Reddit, Discord, Telegram, and more through one connected workspace.
    52 npm
    87
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Schedule and manage social media posts across 10 platforms (Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Threads, Pinterest, Bluesky, Telegram) from any MCP-compatible AI assistant. Supports batch posting, media uploads, analytics, and platform-specific features like Reels, Shorts, and carousels.
    11
    59 npm
    5
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Schedule and manage social media posts across 13 platforms (Bluesky, Threads, Instagram, LinkedIn, Mastodon, YouTube, Facebook, Pinterest, Telegram, Nostr, X/Twitter, Discord, Tumblr and more). OAuth 2.0 + PKCE, 10 tools, draft-first workflow for AI agents.
    10
    13
    AGPL 3.0
  • A
    license
    A
    quality
    B
    maintenance
    Lets any AI agent post to TikTok, Instagram, YouTube, X, LinkedIn, Bluesky, Telegram, Mastodon and Discord through a single post_to_social tool. Connect an account once, then publish everywhere.
    2
    127 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to schedule and publish social media posts to platforms like Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, and Pinterest using natural language.
    33
    99 npm
    3
    MIT

TDQS

A3.8/5.0

Scored across 13 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues