Setup Guide

Connect Crispy to your AI tools in under 2 minutes.

Before you start

  1. Create an account on Crispy
  2. Connect your LinkedIn profile from the dashboard
  3. Generate an API key (starts with lmcp_)
  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

No API key required

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:
MCP Endpoint URL
https://crispy.sh/api/mcp
  1. Claude will redirect you to Crispy to log in and pick a LinkedIn account
  2. Click Approve on the consent screen
  3. Done — Crispy tools are now available in all your Claude.ai conversations

ChatGPT

No API key required

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:
MCP Endpoint URL
https://crispy.sh/api/mcp
  1. Set Authentication to OAuth
  2. ChatGPT will redirect you to Crispy to log in and pick a LinkedIn account
  3. Click Approve on the consent screen
  4. In any chat, click +MoreDeveloper Mode and select your connector

Claude Desktop

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

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:

Terminal
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:

.claude/settings.json
{
  "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:

.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:

MCP Server 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):

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:

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

n8n

n8n Setup
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:
Server URL
https://crispy.sh/api/mcp
  1. Set authentication to Token and paste your API key
  2. Make will auto-discover all available tools with input schemas
  3. 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:
Server URL
https://crispy.sh/api/mcp
  1. Add your API key as a Bearer token in the authorization header
  2. 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:

Terminal
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"
  }'

Built-in Prompts

Crispy includes pre-built workflow prompts. In Claude, these appear as prompt templates you can invoke directly:

inbox_zero

Check unread conversations, summarize them, and draft replies

outbound_prospecting

Search for prospects, review profiles, send personalized invitations

follow_up_sequence

Daily outreach loop: welcome new connections, check pending invitations, follow up on stale conversations

content_engagement

Find high-engagement posts and draft strategic comments

post_drafter

Research what's performing on a topic, then draft posts in 3 formats (list, story, hot take)

competitor_intel

Research a competitor's LinkedIn presence, content strategy, audience, and key employees

weekly_report

Generate a LinkedIn performance report with analytics

network_pulse

See who's active in your network and find engagement opportunities

Available Tools (52)

Your API key's permission scope determines which tools are available.

CategoryTools
Messagingget_my_profile, get_profile, send_invitation, get_connections, list_conversations, get_messages, send_message, start_conversation
Contentcreate_post, get_post, list_posts, react_to_post, comment_on_post, list_post_comments, list_post_reactions, get_post_analytics, get_feed
Searchsearch_people, search_companies, search_posts, get_search_parameters
Outreachsend_inmail, list_pending_invitations, cancel_invitation, list_incoming_invitations, accept_invitation, decline_invitation
Networkget_company_profile, get_profile_viewers
Advancedraw_endpoint

Permission Scopes

Full accessAll 52 tools including raw_endpoint
OutboundMessaging, invitations, InMail, search, connections — no posting
ContentPosts, comments, reactions, feed, analytics — no messaging
Read onlyBrowse profiles, search, read messages, view analytics — no actions

LinkedIn Safety Limits

Crispy enforces daily limits per action type to protect your LinkedIn account:

ActionDaily Limit
Search (people, companies, posts)300/day
Profile views250/day
Messages (send, start, InMail)150/day
Engagement (reactions, comments)100/day
Connection invitations15/day
Posts10/day

Bring Your Own Database

Crispy is stateless — we never store your LinkedIn data. Use our free Starter Kit to set up your own Supabase CRM and markdown campaign templates. You own everything.

Get the Starter Kit