Skip to main content
Glama
NerdSnipe-Inc

postforme-mcp-server

Related Servers

Alternatives to postforme-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to post, schedule, thread, delete, and analyze social media posts across platforms like X, Bluesky, LinkedIn, and Instagram through a single MCP interface.
      241 npm
      MIT
    • 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
    • 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
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Social media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.
      100 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      One prompt, a native post per network, published or scheduled by your agent: TikTok, Instagram, Facebook, YouTube, LinkedIn, Bluesky, Mastodon, Telegram, Discord, Slack, Nostr, X, WordPress, Dev.to, Hashnode. 22 tools incl. plan_week, bulk_schedule, analytics and TikTok video quality check. Priced per brand, not per channel; API + MCP on the free plan. Hosted: postwire.io/api/mcp
      22
      16 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: posts, post results, social accounts, media uploads, webhooks, and previews are all clearly separated. Even the list/single pairs like pfm_get_posts vs pfm_get_post_results are differentiated by their purpose and filters.

    Naming Consistency5/5

    All tool names follow a consistent pfm_<verb>_<object> pattern using snake_case. Verbs are consistently create, get, update, delete, disconnect, and the objects are descriptive, making the API predictable and easy to navigate.

    Tool Count4/5

    With 21 tools, the count is slightly high but justified by the server's clear scope covering three subdomains: posts, accounts, and webhooks. Each tool has a specific purpose and the count is not inflated with redundant operations.

    Completeness5/5

    The surface provides full lifecycle coverage for posts (create, read, update, delete, list, results, previews, media uploads), accounts (create, read, update, disconnect, auth URL, feed), and webhooks (CRUD). The only minor gap is per-post analytics, but pfm_get_account_feed covers metrics when expanded.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues