Integration

Continue

Wire acf-mcp into Continue, the open-source AI assistant extension for VS Code and JetBrains.

iNote

Continue is an open-source AI assistant available as a VS Code and JetBrains extension. MCP support is experimental and limited to a single MCP server per configuration as of today — pick acf-mcp if it is your primary governance server.

!Warning

The experimental.modelContextProtocolServer key may change (singular → plural) in future Continue releases. Check docs.continue.dev before any major upgrade.

Prerequisites

Node.js ≥ 18 (check with node --version)
Continue — continue.dev (VS Code or JetBrains extension)

Install

Open the Continue config file
The file lives at ~/.continue/config.json on macOS/Linux and %USERPROFILE%\.continue\config.json on Windows. Shortcut in the extension: gear icon at the bottom → “Open config.json”.

Add the experimental.modelContextProtocolServer block

Merge with your existing config. Do NOT replace the whole file.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServer": {
      "transport": {
        "type": "stdio",
        "command": "npx",
        "args": ["-y", "acf-mcp"]
      }
    }
  }
}

Reload Continue
Cmd/Ctrl+Shift+P → “Continue: Reload Window” in VS Code. In JetBrains, toggle the Continue sidebar OFF then ON.

Verify

Check the tools are available
In the Continue sidebar, type @: the acf server’s MCP tools should appear in the context picker.
Test prompt
Type: “Use acf.advisor to assess governance of a B2B lead-qualification agent”.
Continue’s reply must cite the tool output with the signed footer (doctrine_hash, doctrine_signature, generated_at).

Advanced config

Environment variables

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServer": {
      "transport": {
        "type": "stdio",
        "command": "npx",
        "args": ["-y", "acf-mcp"],
        "env": {
          "ACF_LOG_LEVEL": "info"
        }
      }
    }
  }
}

Single MCP server limit

If you need multiple MCP servers in parallel, stick with Cursor, Windsurf or Claude Desktop which support an mcpServers dictionary. Continue will lift this limit in a future release.

Transport

Continue supports stdio (transport.type = stdio) or custom transports depending on the version. For stability, keep stdio unless you absolutely need a remote endpoint.

Troubleshooting

@-mention does not show acf. MCP is experimental → check Continue version (≥ 0.9.x). Update the extension from the marketplace.
config.json parse error. Continue does not accept JSON comments. Strip all // and /* */.
Server starts but no tool is callable. Enable “tools” in the current mode (Chat → settings → Tools: ON). Pure autocomplete mode ignores MCP.
Local model without tool-use. If you run a local Llama/Mistral without function-calling support, MCP won’t fire. Switch to Claude/GPT for the conversation where you want ACF.
Silent crash. Open VS Code Developer Console (Help → Toggle Developer Tools) → Console tab. Continue’s MCP errors land there with the [Continue MCP] prefix.