Add Send4 remote MCP server

Open Beginner friendly
#1,908 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, go
Domain
content, devtools

Research direction

Start by reading the registry inclusion heuristics and management docs linked in the issue, then inspect how existing catalog entries are represented in the repository. Add Send4 using its published tool definitions and setup guides as the source, and confirm the entry reflects the stated transport, authentication, and first-party service allowance.

Written by the indexing model from the issue text.

Description

needs-triage

MCP Server Information

Server Name: Send4
Repository URL: https://github.com/send4ai/send4-mcp-server
Brief Description: The official, first-party remote MCP server for Send4, AI SMS and email for sales and support teams. An assistant reads and changes a Send4 workspace (flows, campaigns, conversations, leads, meetings) as the signed-in person.

  • Endpoint: https://mcp.send4.ai/mcp
  • Transport: Streamable HTTP
  • Authentication: OAuth 2.1 with dynamic client registration and PKCE (S256), discovered through the protected-resource metadata in the 401 to an unauthenticated initialize. thv's loopback callback (http://localhost:8666/callback) is accepted.
  • Docs: https://send4.ai/support/ai-assistant-tools/
  • Official MCP Registry: ai.send4/mcp (active)
  • Tools: 64. Every tool's tools/list definition is published in the repository above (tools/).

Workflow it enables

Ask why a lead's conversation went quiet (explain_conversation), read the thread (read_conversation), then improve the flow without touching the live one: duplicate_flow, change the copy with edit_flow, rehearse_flow it, check_flow it, and switch it on. Launching a campaign, switching a flow on or texting a typed number is two tools: a read-only preview_* that returns a summary for the person to confirm, then the write. Reporting tools (get_performance, get_drop_off, get_campaign_report) answer "how are we doing" with links back to the Send4 page.

Limitations, authentication and costs

  • Needs a Send4 workspace on a plan or a started trial, with AI assistants switched on by a workspace admin. Each kind of change (flow editing, campaigns, conversations, team, mailboxes) has its own workspace switch, off by default, and the person picks permissions again on the consent screen.
  • Changes are made as the signed-in person with their role's permissions and are recorded in the workspace audit log as made through an AI assistant.
  • Rehearsing a flow uses the workspace's AI allowance; messages to customers are sent from the workspace's own numbers and mailboxes.

Source and licensing transparency

This is Send4's own first-party service. The hosted server implementation is proprietary. The linked repository is MIT-licensed and holds the setup guides and the published tool definitions, and it says so. This submission relies on the catalog criteria's first-party proprietary-service allowance; it does not present the hosted implementation as open source.

Basic Requirements

  • Open Source: the hosted implementation is proprietary (first-party allowance, see above). The public repository is MIT.
  • MCP Compliant: Streamable HTTP, OAuth 2.1 per the MCP authorization spec.
  • Active Development: maintained by Send4; the repository's tool definitions were updated this week.
  • Documentation: https://send4.ai/support/ai-assistant-tools/ and the repository README.
  • Security Contact: private vulnerability reporting on the repository (SECURITY.md).

Submitter Checklist

Dominant language
Go
Stars
26
Forks
104
Avg merge
1d 4h
Merged PRs (30d)
69

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stacklok/toolhive-catalog

All issues in stacklok/toolhive-catalog

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.