Whatsapp MCP By Timelinesai MCP Server

Drive your **TimelinesAI WhatsApp inbox** from Claude, Cursor, Claude Code, or any MCP-compatible client. List chats, read history, send messages

Remote serverstreamable-http

What is the Whatsapp MCP By Timelinesai MCP server?

If you already use Whatsapp MCP By Timelinesai, the whatsapp mcp by timelinesai mcp server is the piece that lets your assistant work with it directly. Drive your TimelinesAI WhatsApp inbox from Claude, Cursor, Claude Code, or any MCP-compatible client. List chats, read history, send messages, react, label, assign teammates, check quotas — all 18 tools, all as you, all on the same.

What the server does

The TimelinesAI MCP server is a remote control for your real WhatsApp inbox inside TimelinesAI. Connect once via OAuth, then your AI assistant gains 18 tools across chat discovery, messaging, triage (labels + assignments), and workspace introspection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • workspace_quotas — Current plan, seats, messaging + API call quotas, billing period
  • workspace_whatsapp_accounts — Connected WhatsApp accounts (id, phone, owner, status)
  • workspace_team — Teammates, roles, invitation status, account bindings
  • list_chats — Filter chats by status, labels, assignee, group/direct, phone, name, dates, WA account — paginated 50/page
  • chat_details — Full metadata for a single chat
  • chat_history — Conversation context window around a specific message
  • get_chat_messages — Page through messages in a chat
  • message_details — Inspect a single message
  • chat_send_message — Send a message (text, attachment, or reply) in an existing chat
  • whatsapp_account_send_message — Send a message to any phone via a specific WA account (creates chat if none exists — cold send)
  • message_reply — Threaded reply to a specific message
  • message_react — Set or clear an emoji reaction on a message

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

  • A working TimelinesAI production account with at least one connected WhatsApp account in your workspace. Without a connected WA, most tools will return empty or error — the MCP is a remote control for your real inbox, not a sandbox. - Node.js 18+ locally (Cursor / Claude Desktop / Claude Code use npx to launch the mcp-remote proxy). Don't have a TimelinesAI account yet? **[Sign

Where it fits

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Whatsapp MCP By Timelinesai's toolset — workspace_quotas, workspace_whatsapp_accounts, workspace_team and 11 more — is a fair guide to whether it matches your workflow. It is maintained by initechsoftware; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Whatsapp MCP By Timelinesai.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
workspace_quotasCurrent plan, seats, messaging + API call quotas, billing period
workspace_whatsapp_accountsConnected WhatsApp accounts (id, phone, owner, status)
workspace_teamTeammates, roles, invitation status, account bindings
list_chatsFilter chats by status, labels, assignee, group/direct, phone, name, dates, WA account — paginated 50/page
chat_detailsFull metadata for a single chat
chat_historyConversation context window around a specific message
get_chat_messagesPage through messages in a chat
message_detailsInspect a single message
chat_send_messageSend a message (text, attachment, or reply) in an existing chat
whatsapp_account_send_messageSend a message to any phone via a specific WA account (creates chat if none exists — cold send)
message_replyThreaded reply to a specific message
message_reactSet or clear an emoji reaction on a message
chat_openReopen a closed chat
chat_closeClose a chat

How to install the Whatsapp MCP By Timelinesai MCP server

{
  "mcpServers": {
    "whatsapp-mcp-by-timelinesai": {
      "command": "npx",
      "args": ["-y", "mcp-remote"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • A working TimelinesAI production account with at least one connected WhatsApp account in your workspace. Without a connected WA, most tools will return empty or error — the MCP is a remote control for your real inbox, not a sandbox. - Node.js 18+ locally (Cursor / Claude Desktop / Claude Code use npx to launch the mcp-remote proxy). Don't have a TimelinesAI account yet? **[Sign

Example prompts to try

  • Use Whatsapp MCP By Timelinesai to workspace quotas.
  • Use Whatsapp MCP By Timelinesai to workspace whatsapp accounts.
  • Use Whatsapp MCP By Timelinesai to workspace team.

Frequently asked questions

It connects Whatsapp MCP By Timelinesai to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (workspace_quotas, workspace_whatsapp_accounts, workspace_team, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Whatsapp MCP By Timelinesai directly.