Calva Backseat Driver MCP Server

Calva Backseat Driver MCP server exists for a simple reason — assistants are far more useful when they can act on Calva Backseat Driver directly instead of describing what you should do. Make Copilot an Interactive Programmer, tools for VS Code Copilot. Can also be run as an MCP server.

What you get

Clojure Tools for VS Code Agent harnesses. (Such as Copilot and Cursor.)

• Tool: Evaluate Code Access to the Clojure REPL to evaluate code at will. All active REPL sessions in Calva are available for targeting (and with shadow-cljs, also builds and runtime)
• Tool: Create Clojure File Creates Clojure files with automatic bracket balancing
• Tool: Append Code Appends code to Clojure files with automatic bracket balancing
• Tool: Replace Top Level Form Structural editing, including formatting, bracket balancing and linting
• Tool: Insert Top Level Form Structural editing, including formatting, bracket balancing and linting
• Tool: Bracket Balancer Helps the model get the bracket balance right (powered by Parinfer)

What the assistant can call

Once Calva Backseat Driver is connected, these are the calls the assistant has available:

• Tool — Evaluate Code Access to the Clojure REPL to evaluate code at will. All active REPL sessions in Calva are available for targeting (and with
• Resource — Symbol info lookup, (a bit experimental) same as the tool
• calva-backseat — driver.evaluation.maxLength (default 25) — maximum number of items to display in collections. Use 0 to disable length limiting
• Skills — The Skills tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Using — 0. Teach the AI Clojure and REPL discipline, e.g. See: Agent Instructions 1. Connect Calva to your

Configuration and credentials

• VS Code (or your favorite fork) - Calva - Calva Backseat Driver - GitHub Copilot (or some MCP compliant assistant)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Calva Backseat Driver's toolset — Tool, Resource, calva-backseat and 3 more — is a fair guide to whether it matches your workflow. It is maintained by BetterThanTomorrow; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the calva backseat driver mcp server does with a few real requests.