Continue

Continue is an open-source assistant for VS Code and JetBrains. MCP servers are declared in its YAML config.

Add it

Edit ~/.continue/config.yaml:

name: my-configuration
version: 0.0.1
schema: v1

mcpServers:
  - name: vulnetix
    type: streamable-http
    url: https://mcp.vulnetix.com/mcp
    requestOptions:
      headers:
        Authorization: "ApiKey <orgId>:<hex>"

Continue watches the file and reloads on save.

You can also scope it to a workspace with .continue/config.yaml, or express it as a block under .continue/mcpServers/.

Note type: streamable-http here uses hyphens, where Goose uses underscores and the JSON clients use camel case. Copying between them needs the spelling adjusted.

Confirm it works

Switch the chat to Agent mode. MCP tools are not available in Chat or Edit. The tools dropdown lists Vulnetix.

Is there a safe version of lodash without known vulnerabilities?

Worth knowing

Agent mode only, in both the VS Code and JetBrains builds.

Model support. Continue only routes tools to models that support tool calling. If tools are listed but never invoked, check your selected model first, this is the most common cause and looks exactly like a broken server.

YAML quoting. Quote the header value so the colon inside the key is not read as a mapping separator.

Troubleshooting

Server missing. Validate the YAML, because indentation errors fail silently. requestOptions.headers is nested two levels under the server entry.

Tools listed but unused. Agent mode, and a tool-calling model.

401 in results. Both halves of the key, and the whole value quoted.