Skip to main content
Glama
muscled-clients

vibemarketing-mcp

by muscled-clients
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vibemarketing-mcp

No user-submitted related servers found.

    Related Servers

    • viralnote-mcp by viralnote

      viralnote-mcpofficial

      viralnote
      A
      license
      A
      quality
      B
      maintenance
      Gives Claude, Cursor, and any MCP client 15 tools to create, schedule, and publish social posts to TikTok, Instagram Reels, YouTube Shorts, X, Threads, and LinkedIn. Also handles media import by URL or base64, webhooks, and per-platform analytics from the ViralNote API.
      15
      31 npm
      MIT
    • @posteverywhere/mcp by posteverywhere

      @posteverywhere/mcpofficial

      posteverywhere
      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
      774 npm
      4
      MIT

    • postbuzz-mcp

      navneet35371
      A
      license
      B
      quality
      C
      maintenance
      Enables posting, scheduling, and analyzing social media content across 16+ platforms through MCP clients like Claude Desktop, Claude Code, and Cursor.
      51
      28 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a distinct purpose: draft lifecycle (create, get, list, reject, approve variants), calendar views, notifications, and auth utilities. Even similar functions like approve_and_publish_now vs approve_and_schedule are clearly separated by immediate vs scheduled action, and get_calendar_day vs get_calendar_week serve different granularities.

    Naming Consistency4/5

    Tools mostly follow a verb_noun snake_case pattern (get_draft, list_drafts, create_draft, reject_draft). Some deviation exists with compound actions like approve_and_publish_now and utility verbs like ping/whoami/connect, but the style is consistent and readable.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range. Each tool serves a clear function in the workspace workflow: auth, draft management, calendar views, and notifications. No redundancy or excessive compartmentalization.

    Completeness3/5

    Core lifecycle is covered: create, read, approve, reject, publish, schedule, and calendar aggregation. However, there is no update_draft or delete_draft, and no way to cancel a scheduled post or edit an existing draft. Media upload is explicitly unsupported, requiring external URLs. These gaps mean agents cannot handle edits or deletions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources