CLI
Run SendCrew from a terminal or a script with npx sendcrew, and bridge stdio-only MCP clients.
npx sendcrew loginlogin opens SendCrew in your browser. Check that the code matches the one in your terminal, pick the workspace and click Allow access. The CLI saves a workspace API key to ~/.config/sendcrew/config.json (readable only by you). On a server without a browser, run npx sendcrew login --no-browser and open the printed link on any device, or save an existing key with npx sendcrew login --key sc_live_... (--key - reads it from stdin).
Install it globally if you use it often: npm install -g sendcrew. It needs Node.js 18 or later.
Commands
| Command | What it does |
|---|---|
sendcrew senders | Connected senders with status, health and warmup stage |
sendcrew send-connection <profile-url> [--note "..."] | Queue a connection request |
sendcrew send-message <profile-url or thread-id> "<text>" | Queue a message to a connection or into a thread |
sendcrew inbox [--unread] [--limit 10] [--tag interested] | Recent conversations across senders |
sendcrew status <action-id> | Status and result of a queued action |
sendcrew actions [--status failed] [--limit 20] | Recent actions |
sendcrew tools | Every tool, the same names as the MCP server |
sendcrew call <tool> '<json>' | Call any tool, e.g. sendcrew call get_stats '{"range":"30d"}' |
sendcrew whoami | Which key is in use and whether it works |
sendcrew logout | Forget the saved key |
sendcrew mcp | Run a stdio MCP server (see below) |
Options for writes: --dry-run runs every safety check without queueing, --sender <id> picks the sender (by default SendCrew picks the healthiest warm one with quota left) and --campaign <name> groups actions for stats.
Add --json to any command for machine-readable output. Errors are JSON too with --json, and the exit code tells you what happened: 0 done, 1 error, 2 bad usage, 3 blocked by the safety layer (SAFETY_BLOCKED, see errors).
npx sendcrew send-connection https://www.linkedin.com/in/someone/ --note "Loved your post on pricing" --dry-runKeys and environments
The key is picked in this order: --api-key, the SENDCREW_API_KEY environment variable, then the saved config. --base-url (or SENDCREW_BASE_URL) points the CLI at another deployment.
stdio MCP bridge
Some MCP clients only start local servers over stdio. sendcrew mcp is a small stdio server that forwards each message to https://sendcrew.io/api/mcp with your key, so those clients get the same tools:
{
"mcpServers": {
"sendcrew": { "command": "npx", "args": ["-y", "sendcrew", "mcp"] }
}
}It uses the key from npx sendcrew login, or set "env": { "SENDCREW_API_KEY": "sc_live_..." }. Clients that support remote servers should connect to the URL directly instead; see Install.