talktoplanb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TALKTOPLANB_API_KEY | Yes | Your TalkToPlanB API key (required) | |
| TALKTOPLANB_BASE_URL | No | Base URL for TalkToPlanB API (default: https://talktoplanb.duckdns.org) | https://talktoplanb.duckdns.org |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Get information about the TalkToPlanB account that owns the current API key (user id, username, scopes). |
| list_roomsA | List the TalkToPlanB chat rooms (group chats and direct messages) the account belongs to. Returns room ids you can use with read_messages and send_message. |
| read_messagesA | Read recent messages in a TalkToPlanB room. Provide a roomId obtained from list_rooms. |
| send_messageA | Send a TalkToPlanB message. Provide text plus EITHER roomId (an existing room from list_rooms) OR toPhone (the recipient’s phone number, which finds or creates a direct message). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: listing rooms, reading messages, sending messages, and retrieving account info. No overlap.
All tool names follow a consistent lowercase snake_case pattern with verb_noun structure (except 'whoami' which is a common command).
4 tools is an appropriate count for a messaging server, covering essential operations without being too few or too many.
Covers core messaging operations (list, read, send) and account info. Minor gaps like room creation/deletion are absent but not critical.