> ## Documentation Index
> Fetch the complete documentation index at: https://dev.jolts.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# How to connect Cascade

> Configure the Cascade agent's remote Jolts connection.

This guide targets Cascade. The former Windsurf documentation now distinguishes legacy Cascade
from Devin Local; these are not interchangeable configurations.

## Add Jolts

In Cascade's Actions menu, open the MCP configuration file. Merge this entry under `mcpServers`:

```json theme={null}
{
  "mcpServers": {
    "jolts": {
      "serverUrl": "YOUR_MCP_ENDPOINT",
      "headers": { "Authorization": "Bearer ${env:JOLTS_API_KEY}" }
    }
  }
}
```

Copy your company-data endpoint from Jolts' connection guide. Create an [API key](/authentication),
make `JOLTS_API_KEY` available to the editor process, and restart it. Never paste the key into chat.
Enable Jolts in Cascade's MCP controls. Organizational policies may require administrator approval.

## Verify

Ask Cascade to inspect Jolts' tools without searching. Expect `search_companies`, `get_companies`,
and `get_usage`. Call `get_usage` without arguments first; this read is unmetered. Company searches
and lookups require an active or trialing subscription and consume your allowance.

Try [finding active demand](/use-cases/find-active-demand). Review tool inputs before approving.
For authentication failures, check the environment variable and key. For operation errors, use
[troubleshooting](/troubleshooting).

See the [official Cascade configuration guide](https://docs.devin.ai/desktop/cascade/mcp).