Skip to main content

​
Set up the connection

1

Add the SuprSend MCP server

From your regular terminal (not inside a running claude session):
2

Sign in with your SuprSend account

On first connect, Claude Code opens your browser. Sign in with your SuprSend account. Your role decides the tools: admins get every tool, and members get read-only tools except the two that show sent message content, messages_get_content and messages_preview_content.
3

Verify the connection

Start claude and ask:
Claude answers with your SuprSend workspaces.

​
Pin a workspace and restrict tools

By default, Claude can use every workspace and tool your role allows. To keep it on one workspace, or to give it only the tools a job needs, change the URL when you add the server:
  • Pin a workspace by adding its slug to the path. The agent then can’t switch to another workspace:
  • Restrict tools with ?tools=, a comma-separated list of tool names or groups:
See Scope the connection for every URL pattern, and the tool list for every tool.

​
Troubleshooting

If the browser keeps redirecting without completing sign-in, close every Claude window, clear your SuprSend session at app.suprsend.com, and reconnect. For Claude Code, run claude mcp remove suprsend and re-add the server.
Check the workspace slug in the URL. It must match a workspace in your SuprSend account exactly, for example staging, not the workspace’s display name. A slug that doesn’t exist fails with 403 workspace_forbidden. To see your slugs, re-add the server without a slug and ask: “List my SuprSend workspaces.”
Fully quit the app (⌘Q on macOS, Quit from the tray on Windows) and reopen it. Custom connectors only reload on a full restart; closing the window isn’t enough.

Tool list

Every tool, grouped by category, with read vs write labels.

Prompt cheatsheet

Ready-to-use prompts to get started fast.