Skip to main content
Glama
NerdSnipe-Inc

postforme-mcp-server

by NerdSnipe-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to postforme-mcp-server

No user-submitted related servers found.

    Related Servers

    • @chirpie/mcp

      Firefloco
      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.
      1,814 npm
      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
      412 npm
      MIT

    • Outpost

      andrezani
      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.
      13 npm
      MIT

    • PostWire

      Perufitlife
      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
      92 npm
      MIT
    • @crmsolid/mcp-server by Pinlyx

      @crmsolid/mcp-serverofficial

      Pinlyx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage social DM inboxes and posting calendars across 12 platforms, allowing users to triage messages, draft replies, schedule posts, and pull stats from MCP clients.
      51 npm
      5
      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.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

    ActivityStale
    ResponsivenessNo issues

    Resources