> ## 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 VS Code

> Connect Jolts over remote HTTP, keep your API key private, and verify the tool connection.

## Before you start

You need an [API key](/authentication) and the MCP endpoint shown in Jolts' connection guide.
Use the company-data endpoint, not this documentation site's `/mcp` search server.
An active or trialing subscription is required for company operations, but not tool discovery.

## Configure your client

Open **MCP: Open User Configuration** from the Command Palette. Merge the following into that
configuration, replacing `YOUR_MCP_ENDPOINT`. The password prompt keeps your key out of the JSON:

```json theme={null}
{
  "inputs": [
    {
      "type": "promptString",
      "id": "jolts-key",
      "description": "Jolts API key",
      "password": true
    }
  ],
  "servers": {
    "jolts": {
      "type": "http",
      "url": "YOUR_MCP_ENDPOINT",
      "headers": { "Authorization": "Bearer ${input:jolts-key}" }
    }
  }
}
```

Use **MCP: List Servers** to start Jolts. Enter the key when prompted and review the server trust
request. Use Copilot Chat's agent mode and check that Jolts tools are available.
This input-prompt setup targets the standard extension-host chat; Agent Host sessions do not
forward configurations requiring interactive input. See
[VS Code's configuration reference](https://code.visualstudio.com/docs/agents/reference/mcp-configuration).

## Verify before searching

Ask your assistant to list the Jolts tools without running a search. Expect
`search_companies`, `get_companies`, and `get_usage`. Then ask it to call `get_usage`
without arguments to inspect your allowance. That read is unmetered.

Next, try a [company-research workflow](/workflows). Review the tool approval first:
searches and known-company lookups consume your account's allowance.

## Troubleshooting

* No tools: check the endpoint, client trust approval, and workspace policies.
* Unauthorized: check that the bearer header is sent; never paste a key into chat.
* Old tool names: reconnect or refresh discovery after upgrading.
* Tools work but searches fail: read the structured error; check [subscription and limit errors](/troubleshooting).

Return to [all setup options](/mcp-overview) or inspect the [tool reference](/mcp-tools).