Continue.dev

Continue is an open-source AI coding assistant, available as a VS Code and JetBrains extension. It supports remote MCP servers through its config.yaml file (the current format — config.json is legacy and is ignored if a config.yaml is present). Perfai Cloud is a remote server — nothing to install locally, and no npm package to run. Authentication is a custom Bearer header today (not OAuth), since perfai-cloud does not yet publish OAuth discovery metadata.

MCP tools are only available in Continue’s Agent mode — not Chat or Edit mode. Switch modes from the dropdown in the chat input box before expecting Perfai’s tools to show up.

Get an API key

Perfai Cloud authenticates Continue with a Perfai API key. Create one and copy it — Perfai shows the full key only once. You’ll paste it into config.yaml as Bearer pfk_xxxxxxxxxxxx_....

Installation

Global
Workspace-scoped

File: ~/.continue/config.yaml (macOS/Linux) or %USERPROFILE%\.continue\config.yaml (Windows). Registers the server for every workspace.

mcpServers:
  - name: Perfai Cloud
    type: streamable-http
    url: https://mcp-server.perfai.ai/mcp
    requestOptions:
      headers:
        Authorization: "Bearer pfk_xxxxxxxxxxxx_..."

File: .continue/config.yaml at your project root — or a standalone block at .continue/mcpServers/perfai-cloud.yaml. Only active when that workspace is open.

mcpServers:
  - name: Perfai Cloud
    type: streamable-http
    url: https://mcp-server.perfai.ai/mcp
    requestOptions:
      headers:
        Authorization: "Bearer pfk_xxxxxxxxxxxx_..."

Continue nests the auth header under requestOptions.headers, not a flat "headers" key.

config.yaml holds your API key in plaintext — keep it private and out of version control.

Verify the server is connected

Switch the chat mode dropdown to Agent.
Start a new chat and ask it to list its available tools, or check the extension’s output panel (View → Output, select Continue) for a connection error.
If it fails to connect, re-check that the Authorization header is Bearer followed by the full key, with no trailing whitespace, nested under requestOptions.headers as shown above. A 401 means the key has expired or been revoked — create a new one and update the config.

Confirm you’re signed in

The API key signs you in — there is no separate login step. Every tool call runs as the user who created the key, with that user’s organizations and role. In Continue’s chat, type:

What's my Perfai auth status?

It answers with the key’s id (pfk_xxxxxxxxxxxx_…), never the secret. If a tool call fails with 401, the key has expired or been revoked — create a new one and update the connector.

Register an app and run a scan

Register https://your-app.example.com with Perfai

Check the onboarding status for that app

Run a security test on the selected app

Show me the vulnerabilities it found

Fix and verify

Generate an auto-fix plan for all critical and high findings

Mark vulnerability 3 as fixed

Give me the fix summary

Getting Started

Core Concepts

Hybrid Deployment

Changelog

Get an API key

Installation

Verify the server is connected

Confirm you’re signed in

Register an app and run a scan

Fix and verify

​Get an API key

​Installation

​Verify the server is connected

​Confirm you’re signed in

​Register an app and run a scan

​Fix and verify

Get an API key

Installation

Verify the server is connected

Confirm you’re signed in

Register an app and run a scan

Fix and verify