Add Send4 remote MCP server

Aperta Adatta ai principianti
  • Qualcosa non va?
#1,908 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
74/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, go
Ambito
content, devtools

Direzione di ricerca

Inizia leggendo i criteri di inclusione nel registry e la documentazione di gestione collegati nell’issue, poi esamina come sono rappresentate nel repository le voci esistenti del catalogo. Aggiungi Send4 usando come fonte le definizioni degli strumenti e le guide di configurazione pubblicate, e verifica che la voce rispecchi il trasporto, l’autenticazione e l’autorizzazione del servizio first-party indicati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Go
Stelle
25
Fork
95
Merge medio
1g 2h
PR unite (30g)
89

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stacklok/toolhive-catalog

Tutte le issue di stacklok/toolhive-catalog

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.