Messaging

SendSeven MCP Server

The official Model Context Protocol (MCP) server for SendSeven - the unified messaging API platform for WhatsApp, Instagram DMs, Telegram, SMS, Messenger, Live Chat, and Email.

Connect your SendSeven account to Claude, ChatGPT, Gemini, Cursor, or any MCP-compatible AI assistant to manage your unified inbox, send omnichannel messages (WhatsApp, Instagram private replies, Telegram, SMS, Messenger, email), run marketing campaigns, staff a team chat bot, and search your knowledge base using natural language — all through your existing customer support and messaging API platform.

Quick Start

Option 1: Remote Server (Recommended)

No installation needed. Add to your AI client:

Claude Desktop (claude_desktop_config.json):

{

"mcpServers": { "sendseven": { "url": "https://mcp.sendseven.com/mcp", "auth": { "type": "oauth2", "authorizationUrl": "https://mcp.sendseven.com/authorize", "scopes": ["conversations:read", "messages:create", "contacts:read"] } } } }

Claude Code (.claude/settings.json):

{

"mcpServers": { "sendseven": { "url": "https://mcp.sendseven.com/mcp", "headers": { "Authorization": "Bearer YOUR_API_TOKEN" } } } }

ChatGPT (Settings > Connectors > Add custom connector):

MCP Server URL: https://mcp.sendseven.com/mcp

Authentication: OAuth

ChatGPT walks you through the OAuth consent + capability picker automatically — no config file needed.

Option 2: API Token (Developer Setup)

For developers and CI/CD pipelines, use a static API token:

1. Generate an API token in SendSeven: Settings > API Tokens
2. Configure your MCP client with the token as a Bearer header

Option 3: Self-Hosted

git clone https://github.com/SendSeven-GmbH/sendseven-mcp-server.git

cd sendseven-mcp-server npm install npm run dev # Runs on localhost:8787

What Can It Do?

Support Operations

• "Show me open conversations" - List and filter conversations
• "What's the conversation with John about?" - View conversation details
• "Close ticket #123 with notes: refund issued" - Close conversations
• "Assign this to Sarah" - Route to team members

Messaging

• "Send a WhatsApp to +49 170 1234567: Your order is ready" - Multi-channel messaging
• "Email john@example.com about the meeting" - Auto-detect best channel
• "Find all VIP customers" - Contact search

Marketing

• "Create a push notification campaign about our flash sale" - Campaign creation
• "Send an email newsletter to our enterprise list" - Email campaigns
• "How much would a WhatsApp campaign cost?" - Cost estimation

Knowledge Base

• "What does our FAQ say about refunds?" - AI-powered KB search
• "How do I set up WhatsApp integration?" - Self-service answers

Available Tools

Tools are registered based on the capabilities selected during the OAuth connection. The table below groups tools by function for readability; the OAuth consent screen groups the same 69 tools into 12 coarser capability groups (Conversations, Messaging, Email, Contacts, Campaigns, Knowledge Base, Webhooks, Team Chat Bots, Agent Builder, Knowledge Base Authoring, Contact Data Model, Flows) — granting a group grants every tool listed under it below. Full parameter reference: docs/TOOLS.md.

Build an AI agent from your assistant

The Agent Builder lets your own AI assistant create, test and publish a SendSeven Conversational Agent. Ask it to use the build_conversational_agent prompt: it interviews you (website, goals, knowledge, persona, skills, hand-off), writes the knowledge base documents, FAQ and skills, tests the draft and shows the AI credits used. Agents are always created as unpublished, inactive drafts; publishing and switching them on needs your explicit yes (confirm=true). Reference guides are exposed as MCP resources (sendseven://guides/...). If a permission was not granted when you connected, the assistant tells you which capability is missing and asks you to reconnect and approve it (check_permissions).

Authentication

OAuth 2.0 + PKCE (Recommended)

The server is a full OAuth 2.0 authorization server for MCP clients, with Dynamic Client Registration (DCR) so you don't need to pre-register an app:

Most MCP clients (Claude, Cursor, etc.) discover these automatically from https://mcp.sendseven.com/mcp and only need the base URL — see the claude-desktop.json example above and the examples/ directory. For a client that needs the flow spelled out:

1. The client registers itself via DCR (POST /register) and receives a client_id.
2. The client sends the user to /authorize with a PKCE code_challenge and the requested scopes.
3. The user logs in with their SendSeven account and approves the requested scopes on the consent screen.
4. The authorization code is redeemed at /token (with the PKCE code_verifier) for an access + refresh token.
5. The access token is sent as a Bearer token on every MCP request; the server refreshes it automatically using the refresh token.

Users can only grant scopes their SendSeven role already has - a Support Agent without campaign permissions never sees campaign tools, regardless of what the client requests.

The connected account acts as that member: if a workspace admin limited the member's contact visibility ("only reachable contacts"), contact tools only return the contacts that member can reach, and other contacts behave as not found.

API Tokens (Developer)

Generate a token in SendSeven's dashboard (Settings > API Tokens) and pass it as a Bearer header — simpler for CI/CD and scripts, but it doesn't auto-refresh and must be rotated manually.

Claude Skills

The repository includes workflow guides (Skills) that teach AI assistants best practices:

• Campaign Creation - Step-by-step campaign workflow
• Conversation Management - Triage, respond, and resolve
• Contact Messaging - Find contacts and message them
• Team Chat Bots - Post bot messages to Team Chat channels and users

Configuration Examples

See the examples/ directory for configuration files:

• claude-desktop.json - Claude Desktop
• claude-code.json - Claude Code CLI
• cursor.json - Cursor IDE

Pricing

Free for all SendSeven customers. MCP server access is included in every plan.

• Read operations: unlimited (within rate limits)
• Write operations: billed as regular API usage
• Rate limits: 20-500 req/min depending on plan

Development

# Install dependencies

npm install

Run locally

npm run dev

Run tests

npm test

Type check

npm run typecheck

Deploy to Cloudflare Workers

npm run deploy

Security

• OAuth 2.0 with PKCE (no client secret in browser)
• All tokens encrypted at rest
• Scope-based access control (41 granular OAuth scopes, grouped into 12 capability groups for consent)
• Tenant isolation (no cross-tenant data access)
• Rate limiting per plan
• Token revocation via SendSeven settings

License

MIT - see LICENSE

Links

• SendSeven - The unified messaging API
• MCP Specification - Model Context Protocol
• API Documentation - SendSeven REST API