Skip to main content
Glama
Kaption-AI

kaption-whatsapp-mcp

by Kaption-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to kaption-whatsapp-mcp

No user-submitted related servers found.

    Related Servers

    • whatsapp-mcp-local

      VaishnavSPillai03
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Claude with read-only access to your WhatsApp chat history entirely on your local machine, enabling natural language search, summarization, and retrieval of messages without sending data to the cloud.
      21 npm
      MIT

    • whatsapp-mcp-local

      VaishnavSPillai03
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and search your WhatsApp chat history locally with no cloud or API keys, and optionally send audited messages.
      21 npm
      MIT
    • Arara MCP by ararahq

      Arara MCPofficial

      ararahq
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns Claude Code, Claude Desktop, Cursor, Windsurf or ChatGPT into a WhatsApp operator that knows your customers, your templates, your wallet, and your funnel.
      15 npm
      3
      MIT

    • WhatsApp MCP Server

      ai-caseylai
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables seamless integration with WhatsApp through the Model Context Protocol, featuring multi-user support and Supabase cloud storage for persistent message history and media. Users can send messages, search chat records, and manage contacts across platforms like Claude Desktop, Cursor, and OpenClaw.
      -

    • WhatsApp MCP

      adelaidasofia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to interact with WhatsApp: read chats, search messages, send messages with a mandatory confirmation step, and transcribe voice notes locally, all with encrypted storage and prompt-injection scrubbing.
      2
      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.6/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools have distinct purposes, but `query` is a mega-tool whose entities (contacts, conversations, groups, labels, communities) overlap heavily with specialized tools like `list_contacts`, `get_contact`, `get_contact_groups`, `list_groups`, and `get_group`. Additionally `get_analytics` embeds an `export_contacts` section that duplicates the standalone `export_contacts` tool, and `manage_labels` vs `manage_lists` are parallel business/personal variants.

    Naming Consistency4/5

    Strong verb_noun pattern throughout (get_*, list_*, export_*, manage_*, download_*, summarize_*). Two deviations: the bare `query` with no noun, and the noun-only `call_recordings` with no verb, but overall the convention is predictable.

    Tool Count4/5

    18 tools is on the heavier side but reasonable given the breadth of the domain (messaging, contacts, groups, analytics, media, reminders, scheduling, lists, labels, notes, recordings). Each tool maps to a coherent capability area.

    Completeness4/5

    Broad lifecycle coverage across reads, search, media download, chat state, labels/notes/lists, reminders, scheduling, analytics, and call recordings. Notable gaps: no direct/immediate message-send tool (only scheduling) and no group-membership modification (add/remove participants), though most workflows can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources