Skip to main content

​
Set up the connection

1

Add the SuprSend MCP server

Open ~/.cursor/mcp.json to use SuprSend in every project, or .cursor/mcp.json in a project to use it there only:
Add the server under mcpServers:
mcp.json
2

Sign in with your SuprSend account

Ask the agent a SuprSend question in Cursor’s chat. On the first question, Cursor asks you to authenticate and 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

In the chat, ask:
Cursor answers with your SuprSend workspaces.

​
Pin a workspace and restrict tools

By default, Cursor 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 in mcp.json:
  • 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

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, remove the slug, reconnect, and ask: “List my SuprSend workspaces.”
Check that mcp.json is valid JSON and that the SuprSend entry is inside mcpServers. Then ask a SuprSend question in the chat again.

Tool list

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

Prompt cheatsheet

Ready-to-use prompts to get started fast.