Help

Troubleshooting

The fixes for the issues people actually hit. If yours isn't here, reach out and we'll sort it.

My API key is valid but tools aren't appearing in my MCP client

Most clients require a restart after adding a new MCP server. In Claude Desktop, quit and reopen. In Cursor, open the Command Palette → "Reload Window". In Windsurf, restart the IDE. If tools still don't appear, verify the URL is exactly https://crispy.sh/api/mcp and the Authorization header is Bearer YOUR_KEY (with a space, not a colon).

I'm getting 401 Unauthorized errors

Your API key is missing, malformed, or revoked. Make sure the header is Authorization: Bearer crispy_... where the key starts with crispy_. If you recently regenerated a key, update all clients using the old one. Keys are shown once at creation and can't be retrieved.

Claude Code says "Got new credentials, but crispy rejected them on reconnect"

Almost always a stale config in ~/.claude.json. Open the file and look for every mcpServers.crispy entry across the projects map and the root. Three common stale states: (1) Authorization is Bearer ${CRISPY_API_KEY} but the env var is not set, either set it, or remove the headers block to let Claude Code do OAuth automatically; (2) Authorization is Bearer lmcp_..., a legacy prefix from before the rebrand and no longer valid, replace with a fresh crispy_ key; (3) two entries with conflicting auth schemes, keep one. Restart Claude Code after editing.

I'm getting 403 Forbidden on specific tools

The tool is outside your API key's permission scope. Check your account's scope in the dashboard (Accounts → permission badge). Most tools are available on core. Advanced infrastructure tools (webhooks, API keys, warm-up) require full_access. See permission scopes.

LinkedIn session expired, tools return session errors

Your LinkedIn session cookie has expired. Go to the dashboard, find the affected account, and click Reconnect. Sign in again or provide a fresh session cookie using the method shown, then complete any LinkedIn verification. See the LinkedIn connection guide for the full flow.

I hit a safety limit, invitations or messages are blocked

Crispy blocks the action when the cap in force is reached. The defaults include 15 invitations, 150 messages, and 300 searches per day. Counters reset at midnight UTC. Use get_account to check remaining capacity. You can set a lower cap. For invitations, Crispy rejects a cap above 50 per day. For searches and messages, Crispy does not enforce a maximum above the default. These controls do not guarantee against restriction. See safety limits.

search_people returns no results even with broad filters

Your LinkedIn account may not have a Sales Navigator subscription for advanced filters. Basic search works without it, but filters like seniority_level, company_headcount, and years_of_experience require Sales Navigator. Try a simpler query with just keywords and location first.

The MCP server isn't showing up in n8n / Make / Zapier

Make sure you're using a POST request to https://crispy.sh/api/mcp with Content-Type: application/json and Authorization: Bearer YOUR_KEY as headers. In n8n, use the MCP Client node. In Make, use HTTP > Make a request. In Zapier, use Webhooks by Zapier with POST. See the connect guide for exact config.

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

Search documentation