Add Send4 remote MCP server

Abierto Apto para principiantes
  • ¿Algo no está bien?
#1,908 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
74/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, go
Área
content, devtools

Línea de trabajo

Empieza leyendo los criterios de inclusión en el registry y la documentación de gestión enlazados en el issue; después, examina cómo se representan las entradas existentes del catálogo en el repositorio. Añade Send4 tomando como fuente sus definiciones de herramientas y guías de configuración publicadas, y confirma que la entrada refleje el transporte, la autenticación y la autorización del servicio first-party indicados.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Go
Estrellas
25
Forks
95
Merge medio
1 d 2 h
PR fusionados (30 d)
89

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stacklok/toolhive-catalog

Todos los issues de stacklok/toolhive-catalog

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.