mcpField
T
TalkToPlanB

TalkToPlanB

Local
github.com/JMLEE850623Developer Tools0Updated 21w ago
Repository

About TalkToPlanB

TalkToPlanB is an MCP server for AI assistants that need to interact with TalkToPlanB chats. It wraps the developer API to list rooms, read messages, and send them, subject to the API key’s scopes.

Key features

  1. 01Check API key account and scopes
  2. 02List group and direct-message rooms
  3. 03Read recent room messages
  4. 04Send messages by room or phone

Use cases

  1. 01Review recent messages in a chat room
  2. 02Send a message to a room or phone number

MCP support

Exposes TalkToPlanB account, room, and messaging operations as MCP tools over stdio. Access follows the permissions granted to the API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "talktoplanb": {
      "command": "npx",
      "args": [
        "-y",
        "talktoplanb-mcp"
      ],
      "env": {
        "TALKTOPLANB_API_KEY": "<TALKTOPLANB_API_KEY>"
      }
    }
  }
}
Run commandnpx -y talktoplanb-mcp
Environment variables to set
TALKTOPLANB_API_KEYSecretYour TalkToPlanB API key (ttpb_...), created in the developer portal

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmtalktoplanb-mcp1.0.1

Tools

4

Saved tool list · updated 3w ago

This tool takes no parameters.

Details

From the project 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):

{
  "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

cd mcp-server
npm install
npm run build      # compiles src → dist
TALKTOPLANB_API_KEY=ttpb_... npm start

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

cd mcp-server
npm login
npm 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).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.