Crispy MCP server

Crispy — the LinkedIn MCP server for AI agents

Full LinkedIn access for any AI agent, via MCP. Connect Claude, Cursor, Codex, VS Code, JetBrains, n8n, or anything that speaks MCP, and run prospecting, messaging, and campaigns with activity limits built in.

• Website: https://crispy.sh
• MCP endpoint: https://crispy.sh/api/mcp (Streamable HTTP)
• Auth: The remote endpoint supports OAuth directly. Clients that send Authorization can use Bearer .
• Local bridge: npx crispy-mcp (stdio, for clients that cannot send headers)
• Docs & per-client setup: https://crispy.sh/integrations

Crispy is a hosted service, so there is no LinkedIn logic to run locally. This repository holds the connection config plus crispy-mcp, the official stdio bridge: a thin local MCP server that forwards every request to the hosted endpoint with your API key attached.

Which one do I need?

The bridge is a transparent proxy. It does not define its own tools, so every tool Crispy ships is available through it the moment it goes live.

What you can do

Either path gives any AI agent the full LinkedIn surface:

• Find leads — search people and companies, run saved searches, enrich profiles.
• Message — send connection requests, direct messages, and InMail; triage and reply in your inbox.
• Run campaigns — multi-step outreach sequences with paced sending.
• Manage content — draft, schedule, and analyze posts; track engagement.

Every account gets activity limits, plus optional warm-up when enabled.

Quick start

1. Create an account at https://crispy.sh and connect your LinkedIn.
2. Connect your MCP client. Clients that support OAuth sign in directly and hold no key. Clients that send an Authorization header use a Bearer API key from the dashboard instead. The configs below show the API key path.

Claude Code

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

Claude Desktop

Claude Desktop connects remote servers through the Connectors settings: add a custom connector pointing at https://crispy.sh/api/mcp and sign in with OAuth. A client build that cannot do OAuth can send an Authorization: Bearer header instead.

If your build cannot set a header, use the stdio bridge instead. claudedesktopconfig.json:

{
  "mcpServers": {
    "crispy": {
      "command": "npx",
      "args": ["-y", "crispy-mcp"],
      "env": {
        "CRISPY_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Cursor

~/.cursor/mcp.json

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

VS Code

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

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "crispy": {
      "serverUrl": "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 YOURAPIKEY.
4. The node auto-discovers all available tools.

Any HTTP client (verify the connection)

Shortened. The full README is on GitHub.