Crispy

What crispy MCP server does

The crispy MCP server gives AI agents access to LinkedIn functions through Crispy’s hosted service. It is intended for prospecting, outreach, inbox work, and content operations in the 🌐 Social Media category.

Supported workflows include searching for people and companies, running saved searches, and enriching profiles. Agents can send connection requests, direct messages, and InMail, as well as review and respond to inbox activity. Campaign support covers multi-step outreach sequences with paced sending. Content tools can draft, schedule, and analyze posts while tracking engagement.

Accounts have activity limits. Optional warm-up may also be available when enabled for the account. The README describes more than 150 LinkedIn tools available through one API key, without listing each tool individually.

How it works

Crispy hosts the LinkedIn implementation remotely at https://crispy.sh/api/mcp, using Streamable HTTP. Clients that support remote MCP servers and custom headers can connect directly and send an OAuth credential or an Authorization: Bearer <API key> header.

The local crispy-mcp package is a stdio proxy rather than a separate implementation. It receives MCP messages over standard input and output, forwards requests to the hosted endpoint, and attaches the API key. Because it passes methods through instead of maintaining a fixed tool list, newly released Crispy tools can become available through the bridge without updating the local package.

Setup and configuration

Create a Crispy account, connect LinkedIn, and generate an API key from the dashboard before configuring a client. Direct HTTP connections use the hosted endpoint and an authorization header. The README provides configurations for Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, and n8n, with additional setup documentation for JetBrains and Codex.

Use the local bridge when a client only launches local command and args processes or cannot attach request headers. It requires Node 18 or newer and can be started with npx -y crispy-mcp. Set CRISPY_API_KEY in the client environment, or pass an API key with the bridge’s command-line option. CRISPY_MCP_URL can point the bridge at another endpoint, including a local test server.

The bridge intentionally limits failure details by default. CRISPY_MCP_UNSAFE_ERROR_DETAIL=1 restores upstream response content in error messages, but that content could expose credentials if an upstream system reflects them. The setting is disabled for every other value.

Tools and capabilities

The crispy MCP server supports these capability groups:

• Searching people and companies on LinkedIn
• Running saved searches
• Enriching profiles
• Sending connection requests, direct messages, and InMail
• Reviewing and replying to inbox conversations
• Building paced, multi-step outreach campaigns
• Drafting, scheduling, and analyzing posts
• Tracking post engagement

The local bridge exposes the same upstream tools through stdio. It does not define an independent set of tools.

Limitations and notes

Crispy is a hosted service, so LinkedIn logic does not run locally. The bridge needs network access to the Crispy endpoint and a valid API key. Direct remote connections require a client that can handle the endpoint’s authentication method; otherwise, use the stdio bridge.

Activity limits apply to accounts, and campaign sending is paced. The README does not specify the numeric limits, individual tool schemas, or which account plans enable optional warm-up. API keys are sent to Crispy and are not written by the bridge to logs or ordinary error messages. Enabling unsafe error detail changes that protection and should be treated accordingly.