InnerVault

whatsapp-tools

IndexedOfficial MCP Registry, io.github.craft-agent

WhatsApp tools for coding agents: chats, contacts, history, received files, sends and actions.

Open the source (opens github.com) https://github.com/craft-agent/whatsapp-tools

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.

What it is

MCP servers from io.github.craft-agent.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@craftsamo/whatsapp-tools@0.4.0

From the server's entry in the official MCP Registry

Related

  1. WhatsApp tools: wa.me links, QR codes, share widgets, phone validation, API rate card & limits.

    Stale Official MCP Registry, tools.wha Updated 2 months ago 1 note

  2. Samva MCP

    MCP servers

    Authenticated Samva email and WhatsApp tools, including public documentation and template discovery.

    Stale Official MCP Registry, dev.samva Updated 6 days ago 1 note

  3. Safety-first WhatsApp tools: draft-gated sends, enforced rate limits, append-only audit.

    Stale Official MCP Registry, io.github.yolo-labz Updated 2 months ago 1 note

    https://github.com/yolo-labz/wa/releases/download/v2.3.0/wa_2.3.0_darwin_arm64.mcpb
  4. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  5. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  6. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0