Skip to main content
Glama
mrlong0129

yominpost-mcp

by mrlong0129
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to yominpost-mcp

No user-submitted related servers found.

    Related Servers

    • bamf-mcp

      houstongolden
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create, schedule, and analyze LinkedIn and X content, manage ideas, media, and a creator knowledge vault, and run approval-gated outreach campaigns through a hosted MCP endpoint.
      MIT

    • omnipost-social-engine

      1nc0gn30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage social media posts across multiple platforms by scoring virality, generating threads, converting formats, optimizing hooks, scheduling campaigns, and validating platform limits.
      MIT

    • Skryvo

      Skryvo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to write social posts in a brand's voice for up to four platforms, schedule or cancel them, list brands and channels, and read results, all with human approval before anything is published. Connects via OAuth or API key so posts can be planned and managed from Claude, ChatGPT, Cursor, and other MCP clients.
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action on the post lifecycle: generation, risk-checking, platform discovery, draft persistence, and listing. There is a slight question of whether generate_posts persists output, but save_draft explicitly owns persistence, so the boundary is legible.

    Naming Consistency5/5

    All five names follow a consistent verb_noun snake_case pattern (generate_posts, check_post, list_platforms, save_draft, list_posts). The only trivial deviation is singular 'check_post' vs plural 'list_posts', which is still readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for a focused social-post generation and drafting server, with no redundant or filler tools. Each tool covers a distinct stage of the pipeline rather than duplicating capability.

    Completeness4/5

    Core lifecycle coverage is present: generate, validate, save draft, list posts, and discover platforms. Publishing is deliberately delegated to the web UI, but there is no get-single-post, update/edit, or delete tool, which leaves minor lifecycle gaps an agent must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources