WhatsApp Business API MCP Server

Created By
mattcoatswortha year ago
Overview

What is WhatsApp Business API MCP Server?

The WhatsApp Business API MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with the WhatsApp Business API, enabling businesses to send and manage messages effectively.

How to use WhatsApp Business API MCP Server?

To use the server, install it via npm, configure your WhatsApp Business API credentials in a .env file, and start the server using npm commands.

Key features of WhatsApp Business API MCP Server?

  • Send various types of messages (text, template, media, interactive)
  • Manage message templates and media files
  • Update business profile information
  • Manage phone numbers and configure webhooks

Use cases of WhatsApp Business API MCP Server?

  1. Automating customer support through interactive messaging.
  2. Sending promotional messages and updates to customers.
  3. Managing business communications efficiently through templates and media.

FAQ from WhatsApp Business API MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 16 or higher and WhatsApp Business API credentials including API Token, Phone Number ID, and Business Account ID.

  • Is there a way to test the server before going live?

Yes! You can run the server in development mode using npm commands.

  • How can I manage media files?

The server provides tools to upload, get URLs, and delete media files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago