Skip to main content
The plugin runs the SuprSend CLI via npx suprsend, so the only hard prerequisites are Node.js (v20+) and Claude Code.

Prerequisites

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.

Setup

1

Authenticate

Get a service token from Account Settings → Service Tokens.
Or set it as an environment variable for the current session:
2

Install the plugin in your AI tool

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.

Optional: global install

If you’d rather have suprsend on your PATH (faster cold starts, scripting outside the plugin):

CI/CD environments

For automated environments where Claude Code isn’t available interactively, use the SuprSend CLI directly:
The MCP server and plugin are for interactive Claude Code / VS Code Copilot sessions. In CI, call the SuprSend CLI commands directly.

Uninstall

Uninstall the plugin and remove the marketplace:

Usage examples

Make sure the plugin is installed before trying these examples:
Examples marked with (skill) are answered by bundled skills (no API call needed). All others use MCP tools and require authentication.

Workflow management

List and inspect workflows
Create and modify workflows
Compare environments

Schema operations

Template management

CLI reference queries (skill)

These are answered by bundled skills (no API call needed):

Workflow schema reference (skill)

Also powered by bundled skills:

Debugging & troubleshooting

Bulk operations


Troubleshooting

CLI issues

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):
If you’d rather install globally:Fix (macOS):
Fix (Go):
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.
Get a new service token from Account Settings → Service Tokens if needed.

Plugin issues

Try removing and reinstalling the plugin:
  • Claude Code:
  • VS Code Copilot: right-click the suprsend plugin in Agent Plugins → InstalledUninstall, then run Chat: Install Plugin From Source from the command palette and enter suprsend/claude-code-plugin.
  1. Test the server standalone:
    You should see no errors. Press Ctrl+C to stop. (Use suprsend directly if you have a global install.)
  2. Verify the plugin’s .mcp.json exists and contains the suprsend server config.
  3. 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.
  4. Reinstall the plugin (see steps above).
If Claude doesn’t seem to have access to SuprSend tools:
  1. Make sure the plugin is loaded: verify with Claude that the suprsend plugin is active
  2. Try explicitly asking: “Use the suprsend MCP tools to list my workflows”
  3. Check that your CLI profile has the correct permissions

Skills issues

Skills load on demand — they activate when Claude detects you’re working on SuprSend-related tasks. If skills seem missing, try reinstalling the plugin:
Skills are bundled in the plugin repo. To get the latest version, reinstall the plugin — it will pull the latest from the GitHub repo.

Environment-specific

For non-interactive environments, set the SUPRSEND_SERVICE_TOKEN environment variable. The MCP server reads from the same authentication configuration as the CLI.

Getting help