Skip to content

Cursor MCP setup

Selvedge works with any compatible agent. This page covers one optional client integration; see general MCP and CLI setup for other agents.

Cursor speaks MCP natively, so wiring in Selvedge takes one config file. Once it’s connected, the agent can call log_change as it works and prior_attempts before it edits.

Install uv, then install the Selvedge CLI and MCP server:

Terminal window
uv tool install --upgrade selvedge

The MCP config below launches the server with uvx instead of a bare selvedge-server, so the package can be fetched on demand — the editor still needs to find uv installed. Prefer the global binary? Swap uvx --from selvedge selvedge-server for selvedge-server.

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project only):

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

Prefer not to touch config files? selvedge setup detects Cursor and writes this for you (with a .bak first).

Selvedge captures decisions when your agent calls it. Install the instruction block into your project’s .cursorrules:

Terminal window
selvedge prompt --install .cursorrules

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

Open Cursor Settings → MCP. selvedge should be listed with its 8 tools. Or run selvedge watch in a terminal and make a change — the event prints within a second.

These configs run the server with uvx, which ships with uv — so the one prerequisite is uv on the PATH Cursor launches with (curl -LsSf https://astral.sh/uv/install.sh | sh). Prefer a global install instead? pip install selvedge and set command to selvedge-server.