A global suprsend install isn’t required — npx suprsend fetches it on first use and caches it. Installing globally (brew/Go) is supported and takes precedence over the npx fallback.
The plugin format is shared between Claude Code, VS Code Copilot, and GitHub Copilot CLI — pick the install path that matches your editor. The bundled .mcp.json invokes npx -y suprsend start-mcp-server, so the MCP server starts on demand regardless of host.
Preview feature. VS Code Agent Plugins are currently in preview. The host requires the chat.plugins.enabled setting to be on. This setting is managed at the organization level — if it’s disabled, contact your admin to enable it before continuing.
Open the command palette (Cmd/Ctrl + Shift + P).
Run Chat: Install Plugin From Source.
Enter suprsend/claude-code-plugin (or the full URL https://github.com/suprsend/claude-code-plugin.git).
Verify it’s enabled in the Extensions sidebar (search @agentPlugins) under Agent Plugins → Installed.
For team-wide install, commit .github/copilot/settings.json to your project repo:
For automated environments where Claude Code isn’t available interactively, use the SuprSend CLI directly:
# 1. Either: install CLI globallygo install github.com/suprsend/cli/cmd/suprsend@latest# Or: invoke via npx (Node.js is usually available on CI runners)npx -y suprsend --version# 2. Set SUPRSEND_SERVICE_TOKEN as an encrypted secret in your CI provider# 3. Use the CLI directly (no plugin needed)npx suprsend workflow listnpx suprsend sync --from staging --to production
The MCP server and plugin are for interactive Claude Code / VS Code Copilot sessions. In CI, call the SuprSend CLI commands directly.
Right-click the suprsend plugin in Agent Plugins → Installed and choose Uninstall. To remove the workspace marketplace registration, delete the extraKnownMarketplaces.suprsend-marketplace entry from .github/copilot/settings.json (or whichever settings file registered it).
> List all my workflows> Pull the "order-confirmed" workflow and explain each node> Which workflows are currently disabled?
Create and modify workflows
> 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> Add a delay of 30 minutes before the SMS step in "payment-reminder"> Push my local changes to the staging workspace
Compare environments
> Pull "order-confirmed" from both staging and production and show me the differences
> List all schemas in my workspace> Show me the schema for the "invoice" event> Validate this workflow payload against the schema: { "workflow": "purchase-made", "recipients": [...] }> Commit the updated schema for "user-signup"
These are answered by bundled skills (no API call needed):
> What's the CLI command to sync all assets?> How do I switch between workspace profiles?> Show me the full list of CLI commands for workflow management> What flags does the "workflows push" command accept?
> What node types are available in SuprSend workflows?> Show me the JSON schema for a "wait-for-event" node> What are the configuration options for an email channel node?> Give me an example of a conditional branching node
> 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.
> Disable all workflows that contain "test" in their name> Pull all workflows locally so I can review them> List all categories and their translation status
The plugin uses npx suprsend by default, so a global SuprSend CLI install isn’t required — just Node.js v20+ on the system.Fix (npx, recommended):
node --version # should print v20.x or newernpx --versionnpx suprsend --version # fetches + caches the CLI on first run
If you’d rather install globally:Fix (macOS):
brew tap suprsend/tap && brew install --cask suprsend
Fix (Go):
go install github.com/suprsend/cli/cmd/suprsend@latest# Ensure $GOPATH/bin is in your PATH
Authentication errors
MCP tools return 401 or “unauthorized” errors.The CLI resolves authentication in this priority order: (1) SUPRSEND_SERVICE_TOKEN env var, (2) --service-token flag, (3) active profile.
# Option 1: Set environment variableexport SUPRSEND_SERVICE_TOKEN="your_service_token_here"# Option 2: Add or re-add a profile (drop the 'npx' prefix if you have a global install)npx suprsend profile add --name default --service-token <YOUR_SERVICE_TOKEN>
VS Code Copilot: right-click the suprsend plugin in Agent Plugins → Installed → Uninstall, then run Chat: Install Plugin From Source from the command palette and enter suprsend/claude-code-plugin.
MCP server not connecting
Test the server standalone:
npx suprsend start-mcp-server --transport stdio
You should see no errors. Press Ctrl+C to stop. (Use suprsend directly if you have a global install.)
Verify the plugin’s .mcp.json exists and contains the suprsend server config.
Check host-specific logs:
Claude Code: the MCP server output appears in the conversation when tool calls fail.
VS Code Copilot: open the Output panel and select MCP — suprsend from the dropdown.
Reinstall the plugin (see steps above).
Tools not appearing
If Claude doesn’t seem to have access to SuprSend tools:
Make sure the plugin is loaded: verify with Claude that the suprsend plugin is active
Try explicitly asking: “Use the suprsend MCP tools to list my workflows”
Check that your CLI profile has the correct permissions
Skills load on demand — they activate when Claude detects you’re working on SuprSend-related tasks. If skills seem missing, try reinstalling the plugin:
For non-interactive environments, set the SUPRSEND_SERVICE_TOKEN environment variable. The MCP server reads from the same authentication configuration as the CLI.
