Skip to main content
Glama
Kanzando

Mcp-Wacta

by Kanzando
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Mcp-Wacta

No user-submitted related servers found.

    Related Servers

    • wp-mcp

      cnmbdb
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.
      11 npm
      MIT

    • TypeScript WordPress MCP

      bokazio
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WordPress content management that provides a secure interface for AI assistants to interact with WordPress sites, enabling content creation, editing, and media management without destructive operations.
      MIT

    • WordPress MCP Server

      ad02
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that bridges AI assistants to WordPress, enabling natural-language management of posts, pages, media, comments, users, plugins, and settings across multiple sites simultaneously.
      -

    • WAHA MCP

      Ap0c123
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A self-hosted MCP server that connects AI clients to WhatsApp via the WAHA HTTP API. It enables users to manage sessions, search contacts, and send or receive messages and media directly through natural language interfaces.
      18 npm
      -

    • WhatsApp Desktop MCP

      srijonbasak
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects WhatsApp Web to AI tools like Gemini and Claude, providing chat reading, messaging, and a local CRM with draft-and-approve workflows.
      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 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: suite status, settings read/write, CTA CRUD (list/upsert/delete), analytics dashboard vs. CTA inventory, and studio numbers. The two analytics tools are clearly separated by purpose.

    Naming Consistency4/5

    All tools share the wacta_ prefix, but the suffix mixes verb_noun patterns (get_settings, list_ctas) with noun phrases (status, analytics_dashboard, studio_numbers). This is a minor deviation from a purely verb-driven convention.

    Tool Count5/5

    Nine tools is well-scoped for a suite management server, covering configuration, CTA lifecycle, analytics, and numbers without unnecessary bloat or skimping.

    Completeness4/5

    The surface covers suite status, settings management, CTA create/update/delete/list, and analytics reporting. A minor gap is the lack of a dedicated 'get single CTA' endpoint, but list_ctas plus save_cta's upsert behavior mitigate this.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources