Setup Guide

Before you start

1. Create an account on Crispy
2. Connect your LinkedIn profile from the dashboard
3. Generate an API key (starts with crispy_)
4. Copy your API key - it's shown only once

Claude.ai and ChatGPT use OAuth and don't need an API key - just paste the endpoint URL and log in. All other platforms use an API key.

Claude.ai

Connect Crispy directly from Claude.ai using the built-in connector system. Claude handles authentication via OAuth automatically.

1. Go to Claude.ai → Settings → Connectors
2. Click Add Custom Connector
3. Enter the MCP endpoint URL:

https://crispy.sh/api/mcp

4. Claude will redirect you to Crispy to log in and pick a LinkedIn account
5. Click Approve on the consent screen
6. Done - Crispy tools are now available in all your Claude.ai conversations

ChatGPT

Connect Crispy as a custom MCP connector in ChatGPT via Developer Mode. Requires a ChatGPT Pro, Team, Enterprise, or Edu plan.

1. Go to ChatGPT → Settings → Connectors
2. Enable Developer Mode under Advanced settings (workspace admins may need to enable this first)
3. Click Create and enter a name (e.g. "Crispy")
4. Set the MCP Server URL:

https://crispy.sh/api/mcp

5. Set Authentication to OAuth
6. ChatGPT will redirect you to Crispy to log in and pick a LinkedIn account
7. Click Approve on the consent screen
8. In any chat, click + → More → Developer Mode and select your connector

Claude Desktop

Add this to your Claude Desktop MCP config file (claude_desktop_config.json):

{
  "mcpServers": {
    "crispy": {
      "url": "https://crispy.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your actual API key. Restart Claude Desktop after saving.

Claude Code

Add Crispy to Claude Code using the CLI:

claude mcp add crispy -- \
  --url "https://crispy.sh/api/mcp" \
  --header "Authorization: Bearer YOUR_API_KEY"

Or add it to your .claude/settings.json project config:

{
  "mcpServers": {
    "crispy": {
      "url": "https://crispy.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code (GitHub Copilot)

Open the command palette (Ctrl+Shift+P) and run MCP: Open User Configuration. Add this to your .vscode/mcp.json:

{
  "servers": {
    "crispy": {
      "url": "https://crispy.sh/api/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Requires GitHub Copilot with agent mode enabled. Replace YOUR_API_KEY with your actual API key.

Cursor

Go to Cursor Settings → MCP → Add Server, and paste this config:

{
  "mcpServers": {
    "crispy": {
      "url": "https://crispy.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Windsurf

Add this to your Windsurf MCP config file (~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "crispy": {
      "serverUrl": "https://crispy.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Note: Windsurf uses serverUrl instead of url for remote HTTP servers.

JetBrains IDEs

Works with IntelliJ IDEA, WebStorm, PyCharm, and other JetBrains IDEs with AI Assistant. Go to Settings → AI Assistant → MCP Servers and add:

{
  "mcpServers": {
    "crispy": {
      "url": "https://crispy.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

n8n

1. Add an "MCP Client" node to your workflow
2. Set the Server URL to: https://crispy.sh/api/mcp
3. Add a header: Authorization = Bearer YOUR_API_KEY
4. The node will auto-discover all available tools

Make (Integromat)

Use the built-in MCP Client module to connect your Make scenarios to Crispy. Available on all paid plans.

1. Add an MCP Client module to your scenario
2. Enter the server URL:

https://crispy.sh/api/mcp

3. Set authentication to Token and paste your API key
4. Make will auto-discover all available tools with input schemas
5. Map inputs visually and add the module to your workflow

Zapier

Use the MCP Client by Zapier app to connect any Zap to Crispy's tools.

1. Add a MCP Client by Zapier step to your Zap
2. Choose Run Tool as the action
3. Enter the server URL:

https://crispy.sh/api/mcp

4. Add your API key as a Bearer token in the authorization header
5. Select the Crispy tool you want to use and map your inputs

Direct HTTP / cURL

The MCP endpoint speaks JSON-RPC over HTTP. You can call it directly:

curl -X POST https://crispy.sh/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

JSON-RPC Protocol

Crispy uses the Streamable HTTP transport from the MCP specification. All requests are JSON-RPC 2.0 over a single HTTP POST endpoint.

Endpoint

POST https://crispy.sh/api/mcp

Authentication

Pass your API key as a Bearer token. OAuth tokens (from Claude.ai / ChatGPT) are also accepted.

Authorization: Bearer crispy_your_api_key

Available methods

Example: call a tool

curl -X POST https://crispy.sh/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "search_people",
      "arguments": {
        "keyword": "VP Engineering",
        "limit": 5
      }
    }
  }'

Error codes

Available Tools (184)

Your API key's permission scope determines which tools are available. Every tool accepts an optional account_id parameter for multi-account usage.

Crispy exposes 149 AI tools in core scope and 184 REST endpoints total. Tools are consolidated by domain, for example get_campaign aggregates campaign state, stats, health, and outreach config in a single parallel call. Deprecated aliases are maintained for backward compatibility until v6.2.

Built-in Prompts

Crispy includes 8 pre-built workflow prompts. In Claude, these appear as prompt templates you can invoke directly. Use prompts/list to discover them programmatically.

MCP Resources

Resources are read-only data endpoints your AI client can access without calling a tool. Use resources/list and resources/read to access them.

Permission Scopes

Each API key or connected account has a permission scope that controls which tools are available. Set the scope when generating an API key or connecting an account.

LinkedIn Safety Limits

Crispy enforces daily limits per action type to protect your LinkedIn account from restrictions. These limits reset at midnight UTC. Check remaining capacity via the crispy://account/usage resource.

Read-only tools (get_connections, list_posts, get_feed, etc.) have no safety limit.

Webhooks

Get real-time notifications when things happen on your LinkedIn account. Configure a webhook URL and signing secret from your dashboard settings.

Event types (24)

Delivery headers

Payload structure

{
  "id": "evt_a1b2c3d4e5f6g7h8i9j0",
  "event": "invitation.sent",
  "timestamp": "2025-01-15T10:30:00.000Z",
  "webhook_id": "wh_...",
  "account_id": "acc_...",
  "data": {
    "account_name": "Jane Doe",
    "tool_name": "send_invitation",
    "tool_args": { "profile_url": "..." },
    "tool_result": { ... }
  }
}

Signature verification

Always verify the X-Crispy-Signature header to ensure the request came from Crispy.

import { createHmac } from "crypto";

function verifyWebhook(body: string, signature: string, secret: string) {
  const expected = "sha256=" + createHmac("sha256", secret)
    .update(body)
    .digest("hex");
  return signature === expected;
}

// In your webhook handler:
const isValid = verifyWebhook(
  rawBody,
  req.headers["x-crispy-signature"],
  process.env.WEBHOOK_SECRET
);

Retry policy

Failed deliveries are retried up to 5 times with exponential backoff: 1 minute, 5 minutes, 25 minutes, 2 hours, 10 hours. After 5 failed attempts, the delivery is marked as permanently failed.

Campaigns

Crispy supports two outreach modes, depending on how much control you want.

Automated campaigns

Set up a multi-step sequence and Crispy handles the rest. Define your steps (e.g. send connection request, then follow up when they accept, then second follow-up if no reply), and Crispy automatically executes each step at the right time, detects replies, and pauses the sequence when someone responds.

1. Create a campaign with create_campaign
2. Set a follow-up message with update_campaign - this auto-sends when connections accept your invitation
3. Send invitations with campaign_id attached - Crispy tracks everything
4. Sit back - follow-ups, reply detection, and sequencing happen automatically

The easiest way to get started: just say "run campaign_builder" in Claude and it walks you through the whole setup.

Manual outreach with tracking

Prefer to control every message yourself? Just pass a campaign_id when calling outreach tools (send_invitation, send_message, start_conversation, send_inmail) and Crispy tracks the actions for analytics. You decide when and what to send - Crispy only handles tracking.

Campaign tools

Multi-account

You can connect multiple LinkedIn profiles and operate on any of them from a single API key.

How it works

1. Connect multiple LinkedIn profiles from your dashboard
2. Use get_profile_capacity to list all connected accounts and their IDs
3. Pass account_id on any tool call to specify which LinkedIn profile to use
4. Omit account_id to use the default account (the one linked to the API key)

Scope enforcement

Each connected account has its own permission scope. When you use account_id to target a different account, Crispy enforces that account's scope, not your API key's scope. A full_access key cannot bypass a core account's restrictions.

Safety limits

Safety limits are tracked per LinkedIn account, not per API key. Each connected profile gets its own daily limits. Use get_profile_capacity to check remaining capacity across accounts.

Choosing a permission scope

Most users should stay on core. Upgrade to full_access only when you need advanced infrastructure tooling.

All new accounts start on core. You can self-upgrade to full_access at any time via update_account_settings or from the dashboard.

Troubleshooting

Still stuck? Email support or use the contact_support MCP tool to file a ticket directly from your AI client.