TimelinesAI WhatsApp MCP

Drive your real WhatsApp inbox from Claude — read, reply, label, assign.

TimelinesAI WhatsApp MCP connects MCP-compatible clients such as Claude Desktop, Claude Code, Cursor, and other agent tools to your production TimelinesAI WhatsApp inbox. After OAuth authorization, your assistant can list chats, read message history, send replies, react to messages, manage labels, assign teammates, inspect workspace quotas, and work with connected WhatsApp accounts — all as the authenticated TimelinesAI user.

This MCP server controls a real WhatsApp inbox. Messages and changes are production actions, not sandbox actions.

Get started

To use the server, you need a TimelinesAI production account with at least one connected WhatsApp account and Node.js 18+ installed locally. The server runs through mcp-remote, opens a browser authorization flow on first use, and then connects your MCP client to TimelinesAI with OAuth 2.0 PKCE.

Installation

Use this configuration in Claude Desktop, Cursor, Claude Code, or another MCP-compatible client:

{
  "mcpServers": {
    "timelinesai": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.services.timelines.ai/mcp",
        "--host",
        "127.0.0.1"
      ]
    }
  }
}

For Claude Code, you can add the server directly from the CLI:

claude mcp add timelinesai -- npx -y mcp-remote@latest https://mcp.services.timelines.ai/mcp --host 127.0.0.1

After adding the configuration, restart your MCP client. On first use, a browser tab will open for TimelinesAI authorization. Log in, approve access, and your assistant will be able to use the server through your TimelinesAI workspace permissions.

What the server can do

The server exposes 18 tools across workspace metadata, chat discovery, messaging writes, and chat management. A good first prompt after setup is:

What tools does the timelinesai MCP server expose? Group them by purpose and give me one example prompt per group.

Authentication and transport

TimelinesAI WhatsApp MCP uses Streamable HTTP transport and OAuth 2.0 PKCE authentication through mcp-remote. Every action runs as the authenticated TimelinesAI user, and the user’s role permissions in TimelinesAI apply to MCP calls the same way they apply in the TimelinesAI web application.

Production behavior and safety

Messages sent through this MCP server are real WhatsApp messages from your connected TimelinesAI workspace. Recipients cannot distinguish whether a message was sent from the TimelinesAI UI or through an AI assistant. Messaging actions consume the same monthly messaging quota as normal TimelinesAI usage, so teams should check workspace quotas before high-volume actions and confirm before using agents for bulk or sensitive operations.

Useful prompts

Links

Landing page: https://timelines.ai/whatsapp-mcp?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch
Sign up: https://app.timelines.ai/register/?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch&utm_content=listing_footer
Repository: https://github.com/InitechSoftware/whatsapp-mcp-by-timelinesai?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch
Server endpoint: https://mcp.services.timelines.ai/mcp