Skip to main content
Glama
Descomplicar-Marketing-e-Tecnologia

mcp-whatsms-admin

by Descomplicar-Marketing-e-Tecnologia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-whatsms-admin

No user-submitted related servers found.

    Related Servers

    • SendSeven MCP Server by SendSeven-GmbH

      SendSeven MCP Serverofficial

      SendSeven-GmbH
      A
      license
      Not graded
      quality
      C
      maintenance
      WhatsApp, Instagram, Telegram, SMS, Messenger & email in one AI-ready inbox. Manage conversations, send omnichannel messages, run campaigns, sync contacts, and query your knowledge base — 42 tools over a hosted, OAuth-secured MCP server.
      MIT

    • mcp-remnawave

      Nurullaev
      A
      license
      C
      quality
      B
      maintenance
      Enables managing a Remnawave VPN panel from MCP clients, providing tools for users, nodes, subscriptions, statistics, billing, and system operations, plus resources and prompts for common admin tasks.
      190
      7 npm
      MIT

    • personal-whatsapp-mcp

      Gnaneshdivi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables connecting a personal WhatsApp number to any MCP client, providing tools to send, search, and manage WhatsApp messages, with an optional auto-reply feature.
      3
      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.5/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool names a specific resource and action (e.g., users, roles, packages), making their purposes distinct. Even similar operations differ by target resource, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tools follow a strict `whatsms_admin_` prefix with snake_case verb_noun (e.g., `create_user`, `delete_voucher`), ensuring a predictable and consistent pattern.

    Tool Count3/5

    At 27 tools, the set is large, but it covers seven distinct entities plus system operations (cache, languages, health). It's borderline heavy but each tool addresses a separate administrative need.

    Completeness4/5

    The CRUD coverage is solid for primary entities, with minor omissions like no update for subscriptions, no get-by-id endpoints, and transactions only supporting get/delete. These are workable gaps but not fatal.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources