Skip to main content
Glama
enis1998

YaparAI Enterprise MCP Server

by enis1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to YaparAI Enterprise MCP Server

No user-submitted related servers found.

    Related Servers

    • PostMCP MCP Server by postmcp

      PostMCP MCP Serverofficial

      postmcp
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage social media publishing across platforms like LinkedIn, Twitter, Facebook, Instagram, Threads, and Bluesky.
      7
      54 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
      118 npm
      3
      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.
      56 npm
      5
      MIT

    • Sooshie MCP Server

      imjeremyadams
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage social media through Sooshie, including scheduling posts, generating captions, managing accounts, and more via natural language.
      9 npm
      -
    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 22 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource. For example, customer tools (create, get, update, list, note) are separate from social posting (create, delete, list, caption, hashtags) and inbox management (list, read, reply, bulk, AI suggestion). Even overlapping domains like AI reply suggestion vs. reply_to_message are clearly distinguished by generation vs. sending.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., create_customer, list_social_posts, get_social_analytics). No mixing of camelCase or other conventions. The pattern is predictable across all 22 tools.

    Tool Count4/5

    22 tools is slightly above the typical 3-15 range for a well-scoped server, but each tool has a clear purpose and the number is justified by the breadth of functionality (CRM, social posting, inbox, analytics, organization management). It is not excessive and avoids redundancy.

    Completeness4/5

    The tool set covers core CRUD for customers and social posts, inbox interaction, analytics, and AI-assisted features. Minor gaps like missing update for social posts, tag management, or message deletion exist, but the main workflows are well-supported. Agents can accomplish most tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources