Talktoplanb Mcp

io.github.JMLEE850623Published by GitHub account JMLEE850623v1.0.1Updated Oct 25, 2026

MCP server for TalkToPlanB: list rooms, read & send messages (WhatsApp alternative).

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Local MCP server for TalkToPlanB that lets an assistant list chat rooms, read recent messages and send messages through the TalkToPlanB API.

What you can do
Check the account behind the API key (user id, username, scopes). List group chats and direct messages with their room ids. Read recent messages in a room, optionally limited in number. Send a message to a room id or directly to a phone number.
When to use it
Useful when you want an assistant to work with TalkToPlanB conversations: reviewing recent messages in a room, finding room ids, or sending a message to a room or phone number from a desktop MCP client.
Requirements
Runs locally over stdio via npx (npm package talktoplanb-mcp) and needs Node.js 18 or later. Requires a TalkToPlanB API key in the TALKTOPLANB_API_KEY environment variable, created in the developer portal with the messages:read and messages:send scopes. An optional TALKTOPLANB_BASE_URL overrides the default API endpoint. Network access to the TalkToPlanB service is needed.
Before you install
The API key is a secret placed in the client config; anyone with it can act within its scopes. The server can send messages to rooms and phone numbers, so an assistant could message real people. Message content is sent to the TalkToPlanB service. The default endpoint is a non-standard host, so confirm you trust it before pointing the key at it.

Installation

In SourceWeft

  1. Open Talktoplanb Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

TalkToPlanB MCP Server

Let AI assistants (Claude Desktop, and any Model Context Protocol client) use TalkToPlanB — list chat rooms, read messages, and send messages.

It wraps the TalkToPlanB developer REST API and talks MCP over stdio.

Tools

ToolDescription
whoamiAccount info for the current API key (user id, username, scopes).
list_roomsList your group chats and direct messages (returns room ids).
read_messagesRead recent messages in a room (roomId, optional limit).
send_messageSend a message by roomId or toPhone (plus text).

1. Get an API key

  1. Open the developer portal: https://talktoplanb.duckdns.org/portal
  2. Register / log in, create a key, and grant the messages:read and messages:send scopes.
  3. Copy the key (looks like ttpb_xxxxxxxx...).

2. Use it with Claude Desktop

Add this to your Claude Desktop config (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{  "mcpServers": {    "talktoplanb": {      "command": "npx",      "args": ["-y", "talktoplanb-mcp"],      "env": {        "TALKTOPLANB_API_KEY": "ttpb_your_key_here"      }    }  }}

Restart Claude Desktop, then try: “List my TalkToPlanB rooms” or “Send a TalkToPlanB message to +60123456789 saying hello.”

Environment variables

VariableRequiredDefault
TALKTOPLANB_API_KEY✅—
TALKTOPLANB_BASE_URL❌https://talktoplanb.duckdns.org

3. Local development

bash
cd mcp-servernpm installnpm run build      # compiles src → distTALKTOPLANB_API_KEY=ttpb_... npm start

4. Publish to npm (so npx talktoplanb-mcp works for everyone)

bash
cd mcp-servernpm loginnpm publish --access public

After publishing, you can list it on MCP registries (mcp.so, Glama, Smithery) — see ../marketing/listing-checklist.md.

Notes

  • Requires Node.js 18+ (uses the built-in fetch).
  • stdout carries the MCP protocol; all logs go to stderr.
  • The server only does what your API key is allowed to do (its scopes).

Source: README.md at commit cbbb68d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts