Agent Plugin

Install the SuprSend plugin in Claude, VS Code, GitHub Copilot CLI, Codex, Cursor, or Kiro. The plugin wires in the hosted MCP server and the SuprSend skill.

The SuprSend plugin wires the hosted SuprSend MCP server (https://mcp.suprsend.com/mcp) into your AI client in one step and adds the suprsend skill that tells the agent when to call which tool. Nothing runs on your machine; sign in with your SuprSend account.

Two plugin packages cover every supported client:

Plugin	Clients
suprsend/claude-plugin	Claude on the web, Desktop, mobile, Cowork, and Claude Code.
suprsend/agent-plugin	VS Code, GitHub Copilot CLI, Codex, Cursor, Kiro, and other Agent Plugins 1.0.0 clients.

No API key, no service token. Sign-in uses OAuth via WorkOS. The agent gets the same permissions your role has in the SuprSend dashboard.

Install

Claude Code

/plugin marketplace add suprsend/claude-plugin
/plugin install suprsend@suprsend

Then sign in once: run /mcp, select suprsend, and choose Authenticate.

A plugin that you install on claude.ai also appears in Claude Code as a synced plugin.

Claude on web / Desktop / mobile / Cowork

1. Open Customize → Plugins → Add → Add marketplace, and enter suprsend/claude-plugin.
2. Install the suprsend plugin.
3. Open the plugin’s Connectors tab, and connect suprsend. Sign in with your SuprSend account.

On Team and Enterprise plans, an owner may need to allow the connector first.

VS Code

VS Code Agent Plugins are a preview feature. The host requires the chat.plugins.enabled setting to be on; it’s managed at the organization level. If it’s disabled, contact your admin.

1. Open the Command Palette (Cmd/Ctrl + Shift + P).
2. Run Chat: Install Plugin From Source.
3. Enter the URL:

https://github.com/suprsend/agent-plugin

VS Code asks you to sign in when the server starts.

GitHub Copilot CLI

Requires Copilot CLI 1.0.83 or later.

copilot plugin install suprsend/agent-plugin

Copilot CLI asks you to sign in on first use.

Codex

codex plugin marketplace add suprsend/agent-plugin

Install suprsend from the marketplace, then sign in:

codex mcp login suprsend

Cursor

Customize → Plugins → Add → From GitHub Repository, and paste:

https://github.com/suprsend/agent-plugin

Cursor sign-in is not yet available. Cursor signs in to remote MCP servers only through Dynamic Client Registration (DCR); the SuprSend server uses Client ID Metadata Documents (CIMD). Until Cursor supports CIMD, the plugin registers the server but can’t complete the sign-in handshake.

Kiro

Powers → Add Custom Power → Import power from GitHub →

https://github.com/suprsend/agent-plugin

Kiro sign-in is not yet available by default. Kiro uses Dynamic Client Registration; the SuprSend server uses Client ID Metadata Documents (CIMD).

Limit the scope

To fix one workspace or a set of tool groups, add the server with a custom URL instead of the plugin’s default:

• https://mcp.suprsend.com/mcp/staging — only the staging workspace.
• https://mcp.suprsend.com/mcp?tools=users.*,lists.* — only the listed tool groups.

See the tool list for the full group reference.

Moving from suprsend/claude-code-plugin

suprsend/claude-plugin replaces the older suprsend/claude-code-plugin marketplace. The old marketplace forwards to the new plugin, so existing users can move with:

/plugin marketplace update suprsend-marketplace

For a clean setup, remove the old marketplace and add suprsend/claude-plugin.

---

Usage examples

Once the plugin is installed and signed in, prompt the agent in natural language:

List my SuprSend workspaces.

Why did user usr_8f3k2m not get the "order-confirmed" email yesterday?

How many emails did we send per day last week, in production?

Opt user usr_8f3k2m out of the newsletter category and stop SMS for them.

Make the static list beta-testers exactly the users in this CSV.

Create a workflow that sends the "welcome" email when the event USER_SIGNUP comes in.

Workflow management

> List all my workflows

> Pull the "order-confirmed" workflow and explain each node

> Which workflows are currently disabled?

> Create a workflow called "welcome-series" that:
  1. Sends a welcome email immediately
  2. Waits 24 hours
  3. Sends a follow-up SMS if the email wasn't opened
  4. Falls back to push notification after 2 more hours

Delivery analytics

> Show me the email delivery rate by tenant for the last 7 days as a line chart.

> Which workflows failed most often this week?

Template management

> What email templates do I have?

> Show me the variables used in the "welcome-email" template

> Publish the "quote-expiring" template so the new email variant goes live.

Debugging

> Why might my "payment-reminder" workflow not be triggering?

> Check if the "welcome-series" workflow is enabled

> What events are configured in my workspace? I think I might be
  missing the "user-signup" event.

---

CI/CD

The plugin and MCP server are for interactive AI-client sessions. For CI, use the SuprSend SDKs or the Agent SDK.

---

Troubleshooting

OAuth sign-in loop

If the browser keeps redirecting without completing sign-in, close every AI-client window, clear your SuprSend session at app.suprsend.com, and reconnect. For Claude Code, run /mcp, select suprsend, and re-authenticate.

Plugin marketplace not found

Confirm the marketplace name is exactly suprsend/claude-plugin or suprsend/agent-plugin. The old suprsend/claude-code-plugin marketplace forwards to the new one; if you still see 404s, remove the old marketplace and add the new one directly.

Cursor or Kiro: sign-in says 'not yet'

The SuprSend MCP server signs clients in through Client ID Metadata Documents (CIMD). Cursor and Kiro currently sign in only through Dynamic Client Registration (DCR). Until they support CIMD, the plugin registers the server for you but can’t complete the sign-in handshake. Use another client (Claude, VS Code, Codex, Gemini, Windsurf) in the meantime.

Server shows disconnected

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.”

---

Uninstall

Claude Code

/plugin uninstall suprsend@suprsend
/plugin marketplace remove suprsend

VS Code

Right-click the suprsend plugin in Agent Plugins → Installed and choose Uninstall.

Other clients

Remove the plugin from the client’s plugin or MCP settings. Removing the plugin does not sign you out of SuprSend; sign out at app.suprsend.com if you need to end the OAuth session too.

---

Getting help

• SuprSend Documentation
• SuprSend Slack Community
• GitHub Issues — Claude plugin
• GitHub Issues — Agent plugin
• GitHub Issues — MCP server