Skip to content
selvedge

Add Selvedge to Continue

Continue configures MCP servers in YAML. Add a selvedge entry under mcpServers and the assistant can call Selvedge’s tools in agent mode.

Before you start

Section titled “Before you start”

pip install selvedge gives you the selvedge CLI (selvedge setup, selvedge blame, and the selvedge prompt helper below):

Terminal window
pip install selvedge

The MCP config below launches the server with uvx instead of a bare selvedge-server, so it starts reliably even when your editor doesn’t share your shell’s PATH — it just needs uv installed. Prefer the global binary? Swap uvx --from selvedge selvedge-server for selvedge-server.

Add the MCP server

Section titled “Add the MCP server”

Add this to ~/.continue/config.yaml (global) — or a workspace file under .continue/mcpServers/:

mcpServers:
  - name: selvedge
    command: uvx
    args: ["--from", "selvedge", "selvedge-server"]

Tell your agent when to call it

Section titled “Tell your agent when to call it”

Selvedge only captures the why if your agent knows to call it. Install the one-block instruction set into your project’s CLAUDE.md / .cursorrules:

Terminal window
selvedge prompt --install CLAUDE.md

It’s also a copy-paste block on the site: the Selvedge agent prompt block.

Verify

Section titled “Verify”

Switch Continue to Agent mode and open its tools list — the selvedge tools should be available. (MCP tools are only callable in agent/chat-with-tools mode.)

If it doesn’t connect

Section titled “If it doesn’t connect”

Continue’s YAML config supports stdio servers only (which is all Selvedge needs). Keep the two-space indentation exactly as shown — YAML is whitespace-sensitive. The config calls uvx, so uv must be installed (or pip install selvedge and use command: selvedge-server).

Next

Section titled “Next”