Setting up in Cursor, VS Code, Windsurf, and JetBrains

All four editors connect to the same endpoint, https://crispy.sh/api/mcp, authenticated with an API key from your dashboard. The config key names differ slightly per editor, and that is the part that trips people up.

Cursor

Go to Cursor Settings, then MCP, then Add Server, and paste:

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

VS Code

Run 'MCP: Open User Configuration' from the command palette, or edit .vscode/mcp.json. VS Code uses a servers key instead of mcpServers, and requires "type": "http":

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

Requires GitHub Copilot with agent mode enabled. Once connected, ask for anything on LinkedIn from Copilot Chat in agent mode.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json. Windsurf uses serverUrl instead of url for remote HTTP servers:

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

JetBrains

Works with IntelliJ IDEA, WebStorm, PyCharm, and other JetBrains IDEs with AI Assistant. Go to Settings, then Tools, then AI Assistant, then Model Context Protocol (MCP), and click Add. Choose the HTTP connection and enter the Crispy endpoint with your bearer token, or paste the same JSON shape as Cursor.

After connecting

The editor auto-discovers every LinkedIn tool, no per-tool setup needed. Generate or rotate API keys anytime in the dashboard under API Keys. If a connection stops working after a key rotation, update the key in the config above and reload the editor's MCP connection.