ReachDirect MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BREVO_API_KEY | Yes | Brevo → Settings → SMTP & API → API keys. The free plan sends 300 emails/day. | |
| REACHDIRECT_STATE_DIR | No | WhatsApp browser profile, daily counters, do-not-contact list. | ~/.reachdirect |
| REACHDIRECT_OUTPUT_DIR | No | `outreach_contacts.xlsx` and the WhatsApp QR page. | Desktop, else ~/ReachDirect |
| REACHDIRECT_DAILY_LIMIT | No | Max sends per channel per day. | 50 |
| REACHDIRECT_BROWSER_CHANNEL | No | Use `msedge` or `chrome` to drive an installed browser instead. | bundled Chromium |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| preview_messageD | Fill {{first_name}}, {{name}}, {{company}} and any extra {{placeholders}} (fallbacks: {{first_name|there}}). |
| send_emailB | Send one email through Brevo (needs BREVO_API_KEY and a sender verified in Brevo). |
| send_whatsappA | Send one WhatsApp message through WhatsApp Web (a browser window opens; first run asks for a QR scan). |
| save_outreach_contactB | Append a row to outreach_contacts.xlsx (Date, Name, Company, Email, Phone, Channel, Status, Notes). |
| list_outreach_contactsC | Latest rows of the outreach log. |
| add_do_not_contactB | Record that someone asked not to be contacted. Future sends to them are refused. |
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 6 tools
Each tool has a distinct action target: listing rows, previewing templates, sending via two clearly separated channels, appending rows, and recording DNC. Minor blur between list_outreach_contacts (outreach log) and save_outreach_contact (outreach_contacts.xlsx), which appear to touch the same data under different resource names.
All six names are snake_case verb_noun (list_, preview_, send_, save_, add_) with predictable patterns, including the parallel send_email/send_whatsapp pair.
Six tools cover the core read/send/save/suppress flow without bloat. The set is slightly thin — there is no status-update or lookup tool — but each tool clearly earns its place.
The surface handles listing, templating, sending on two channels, saving, and DNC, but the Status field in the saved row has no update tool, there is no way to remove or inspect DNC entries, and no contact lookup/search or reply tracking. These gaps will leave agents unable to close the loop after a send.