TimelinesAI WhatsApp

Created By
TimelinesAI21 days ago
Connect your TimelinesAI WhatsApp inbox to Claude. List chats, read history, send messages, react, label, assign teammates — all as you, in production.
Overview

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

ResourceLink
TimelinesAI WhatsApp MCP landing pagehttps://timelines.ai/whatsapp-mcp?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch
Sign up for TimelinesAIhttps://app.timelines.ai/register/?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch&utm_content=listing_cta
GitHub repositoryhttps://github.com/InitechSoftware/whatsapp-mcp-by-timelinesai?utm_source=mcp.so&utm_medium=directory&utm_campaign=mcp_launch
MCP server endpointhttps://mcp.services.timelines.ai/mcp

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

Capability areaTools and actions
Workspace introspectionCheck plan, seats, messaging quotas, API call quotas, billing period, connected WhatsApp accounts, teammates, roles, and account bindings.
Chat discovery and inspectionList chats, filter by labels, assignee, status, WhatsApp account, phone, name, and dates; inspect chat details, message history, and individual messages.
MessagingSend messages in existing chats, send outbound messages through a selected WhatsApp account, reply to specific messages, and add or clear emoji reactions.
Chat operationsOpen or close chats, assign or unassign teammates, add labels, and remove labels for inbox triage workflows.

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

Use caseExample prompt
Inbox overviewShow me open WhatsApp chats assigned to me and summarize which ones need a reply.
Customer support triageFind chats with unresolved customer questions, label them as support, and suggest next replies before sending anything.
Team handoffWhich teammates are available in my workspace, and which chats should be reassigned based on the latest conversation context?
Quota checkShow my current TimelinesAI workspace messaging and API quotas before I send any outbound messages.

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

Server Config

{
  "mcpServers": {
    "timelinesai": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.services.timelines.ai/mcp",
        "--host",
        "127.0.0.1"
      ]
    }
  }
}
Project Info
Created At
21 days ago
Updated At
21 days ago
Author Name
TimelinesAI
Star
-
Language
-
License
-
Category

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)

21 hours ago