The SuprSend MCP server is Beta. Since LLM behavior can vary and responses aren’t always deterministic, we recommend starting with a development workspace before rolling it out in production.
The SuprSend MCP server exposes key SuprSend components—such as workflows, users, tenants, objects, and preferences—through the Model Context Protocol. With MCP, your AI agents can directly query, update, and manage SuprSend resources, as well as trigger notifications, all through tool calling.

​
What can you do with MCP?

Here are some examples of how you can use MCP server for building with LLM and SuprSend:
  • Search documentation and apply results. “Find the setup guide for integrating the React Drop-in Inbox and insert the required code snippet into my project.”
  • Trigger workflows on demand. “Run the approval-required workflow for user John Doe to test my notification setup.”
  • Bootstrap test data. “Create a sample user named John Doe and a tenant called acme-corp in my workspace.”
  • Manage notification preferences. “Enable email notifications for marketing team and disable SMS.”
  • Configure tenant-level branding. “Update the logo and primary color for the enterprise tenant to match the new design guidelines.”

​
Authentication

The MCP server requires a Service Token for authentication. Generate one from your SuprSend dashboard: Account Settings -> Service Tokens.

​
Starting MCP Sever from CLI

suprsend start-mcp-server

# Start MCP server with specific tools using SSE transport
suprsend start-mcp-server --tools "users,tenants" -t sse
Flags include:
  • --tools – restricts which tools are available (recommended).
  • --transport – transport to use (stdio or sse).

​
Setting it up in Claude

  1. Open Claude Settings → Developer Section.
  2. Click Edit Config under Local MCP Servers.
  3. Add the following snippet:
{
  "mcpServers": {
    "suprsend": {
      "command": "suprsend",
      "args": [
        "start-mcp-server",
        "--service-token", "YOUR-SERVICE-TOKEN"
      ]
    }
  }
}

​
Setting it up in Cursor

  1. Go to Cursor -> Settings -> Cursor Settings
  2. On the settings modal, Go to MCP & Integrations and click on “New MCP Server”.
  3. Inside mcp.json file, add below code:
{
  "mcpServers": {
    "suprsend": {
      "command": "suprsend",
      "args": [
        "start-mcp-server",
        "--service-token", "YOUR-SERVICE-TOKEN"
      ]
    }
  }
}

​
Setting it up in Windsurf

  1. Open Windsurf settings → Extensions.
  2. Add the SuprSend MCP configuration:
{
  "suprsend": {
    "command": "suprsend",
    "args": ["start-mcp-server", "--service-token", "YOUR-SERVICE-TOKEN"],
    "name": "SuprSend MCP Server"
  }
}

​
Tool List

Here’s a list of all tools available in the MCP server. We’ll keep adding more tools to this list as we build out the MCP server:
TOOL TYPETOOL NAMETOOL DESCRIPTION
documentationdocumentation.searchSearch across SuprSend documentation for relevant topics or examples.
documentationdocumentation.fetchRetrieve the full content of a specific documentation page by its URI.
objectsobjects.getFetch details for a specific object by ID or key.
objectsobjects.upsertCreate a new object or update an existing one.
objectsobjects.get_subscriptionsView all subscriptions associated with an object.
objectsobjects.upsert_subscriptionsAdd or update subscriptions for an object.
objectsobjects.get_preferencesRetrieve an object’s preferences, optionally filtered by category.
objectsobjects.update_preferencesUpdate category-level preferences for an object.
tenantstenants.getFetch information about a specific tenant.
tenantstenants.upsertCreate a new tenant or update an existing one.
tenantstenants.get_preferencesRetrieve all category preferences for a tenant.
tenantstenants.update_preferencesUpdate category-level preferences for a tenant.
usersusers.getFetch information about a specific user.
usersusers.upsertCreate a new user or update an existing one.
usersusers.get_preferencesRetrieve a user’s preferences, optionally filtered by category.
usersusers.update_preferencesUpdate category-level preferences for a user.

​
Configuring the available tools

By default, the MCP server exposes all tools. In most cases, you won’t want to grant your AI agent access to everything—especially in production. Instead, you can control which tools are available by using the --tools flag when starting the MCP server. This helps ensure the agent only interacts with the resources it actually needs. The --tools flag accepts one or more tool identifiers in the format tool_type.tool. You can also use a wildcard () to enable all tools of a type. For example, users. will allow access to all user-related tools, while users.get_preferences will expose only that single tool. Here’s an example of how to pass tool configuration: 
{
  "suprsend": {
    "command": "suprsend",
    "args": [
      "start-mcp-server",
      "--tools", "users.createUser",
      "tenants.*",
      "--service-token", "YOUR-SERVICE-TOKEN"
    ],
    "name": "SuprSend MCP Server"
  }
}