Skip to main content

Connect other MCP clients

Any client that speaks the Model Context Protocol can use SendSeven. The server is hosted by SendSeven; there is nothing to install.

SettingValue
Server URLhttps://mcp.sendseven.com/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.0 with PKCE and dynamic client registration. Your client opens the SendSeven sign-in automatically
MCP Registry namecom.sendseven/messaging

On first use your client opens a browser window where you pick the capabilities to grant, sign in to SendSeven, choose the workspace and approve. Tokens refresh automatically.

Claude Code​

claude mcp add --transport http sendseven https://mcp.sendseven.com/mcp

Run /mcp in Claude Code, select sendseven and choose Authenticate. Details: Use SendSeven in Claude.

Claude Desktop​

Use the official connector: in Claude Desktop open Settings > Connectors, search for SendSeven and click Connect (or open the directory listing). Connectors added on claude.ai show up in the desktop app automatically. See Use SendSeven in Claude.

Cursor​

Add to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:

{
"mcpServers": {
"sendseven": {
"url": "https://mcp.sendseven.com/mcp"
}
}
}

Open Cursor Settings > MCP and click Login next to sendseven to complete the sign-in.

VS Code (GitHub Copilot)​

Add to .vscode/mcp.json in your workspace:

{
"servers": {
"sendseven": {
"type": "http",
"url": "https://mcp.sendseven.com/mcp"
}
}
}

Start the server from the file (or with MCP: List Servers) and follow the sign-in prompt. Use Copilot Chat in agent mode to call the tools.

OpenAI Codex​

codex mcp add sendseven --url https://mcp.sendseven.com/mcp
codex mcp login sendseven

Or add it to ~/.codex/config.toml:

[mcp_servers.sendseven]
url = "https://mcp.sendseven.com/mcp"

Windsurf​

Add to ~/.codeium/windsurf/mcp_config.json:

{
"mcpServers": {
"sendseven": {
"serverUrl": "https://mcp.sendseven.com/mcp"
}
}
}

Gemini CLI​

Add to ~/.gemini/settings.json:

{
"mcpServers": {
"sendseven": {
"httpUrl": "https://mcp.sendseven.com/mcp"
}
}
}

Then run /mcp auth sendseven in Gemini CLI to sign in.

Clients that only support local (stdio) servers​

Bridge to the remote server with mcp-remote (requires Node.js):

{
"mcpServers": {
"sendseven": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.sendseven.com/mcp"]
}
}
}

mcp-remote opens the SendSeven sign-in in your browser on first start.

Test the connection​

Ask your assistant:

"Check my SendSeven permissions."

It runs check_permissions and lists the capabilities you granted and the ones that are missing. Then try:

"List my connected SendSeven channels and the open conversations that need a reply."

Permissions and troubleshooting​

  • The assistant acts as you. One connection is one member in one workspace. It cannot exceed your role or reach other workspaces.
  • permission_missing: the capability was not granted. Remove SendSeven from your client, add it again and approve that capability. You also need to reconnect once after we add new capabilities.
  • forbidden: your workspace role does not allow the action. Ask a workspace admin.
  • reauthorization_required: the sign-in expired or was revoked. Sign in again from your client.
  • Revoke access at any time in SendSeven under Settings > Connected Apps.

All error codes: MCP server reference.