Skip to Content
SendCrew

Quickstart

Connect a LinkedIn account, create an API key and send your first action.

Connect a sender

In the dashboard, open Accounts and connect a LinkedIn account with the SendCrew Chrome extension. The extension only reads your session; it never clicks or types on LinkedIn pages.

Don't sign out of that account

Signing out of LinkedIn in that browser ends the session SendCrew uses, and the sender pauses until you reconnect. Give each LinkedIn account its own Chrome profile, and switch profiles instead of signing out.

Create an API key

Open API keys and create a key. Keys belong to one workspace (one client), so an agent with that key only sees that client's senders, contacts and inbox.

Add SendCrew to your agent

Pick your agent below.

Connect your agent

Pick your agent and paste in your API key. Each one connects to the same MCP server, https://sendcrew.io/api/mcp, and sees the same tools.

One command adds SendCrew to every project.

  1. 1
    Create an API keyDashboard → API keys. A key belongs to one client workspace, so the agent only sees that client's accounts.
  2. 2
    Add the server
    Terminal
    claude mcp add --transport http --scope user sendcrew https://sendcrew.io/api/mcp \
      --header "Authorization: Bearer sc_live_YOUR_KEY"
  3. 3
    Check it's connectedRun /mcp in Claude Code. SendCrew should show as connected with its tools. No key handy? Leave out --header and choose Authenticate in /mcp to sign in with OAuth.

The response to any write holds an action_id. Check it with get_action_status, or subscribe to webhooks.

Try it without sending

Add "dry_run": true to any write. SendCrew runs every safety check and tells you what would happen, without queueing anything.