Skip to content

Connect an assistant

Quiver reaches your assistant through one MCP server, quiver mcp. You set it up once per assistant; the assistant starts it for each session.

Terminal window
quiver install

This sets up every supported assistant that is installed. Name assistants to set up only those:

Terminal window
quiver install codex cursor

Next to the MCP server, quiver install sets up a session-start hook for Claude Code, Codex, Cursor, Antigravity and VS Code, and a sub-agent hook where the assistant has one. The hook is how always-on skills reach the model. Claude Desktop has no hook. See Always-on skills.

AssistantNameWhat quiver install changes
Claude Codeclaude-codeRuns claude mcp add --scope user quiver -- <path to quiver> mcp, and adds the session-start and sub-agent hooks.
CodexcodexRuns codex mcp add quiver -- <path to quiver> mcp, which writes ~/.codex/config.toml (or $CODEX_HOME), and adds the session-start and sub-agent hooks. The Codex CLI and app share them.
CursorcursorAdds quiver to mcpServers in ~/.cursor/mcp.json, and adds the session-start hook.
Claude Desktopclaude-desktopAdds quiver to mcpServers in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). It has no hook.
AntigravityantigravityAdds quiver to mcpServers in ~/.gemini/config/mcp_config.json, which the Antigravity CLI (agy) reads, and adds the session-start and sub-agent hooks.
VS Code CopilotvscodeAdds quiver to servers in ~/Library/Application Support/Code/User/mcp.json (macOS; %APPDATA%\Code\User\mcp.json on Windows, ~/.config/Code/User/mcp.json on Linux), with "type": "stdio", and adds the session-start and sub-agent hooks in ~/.copilot/hooks/quiver.json.

An assistant counts as installed when its command (claude, codex) is on PATH, or when its config folder exists (~/.gemini/antigravity-cli for Antigravity, VS Code's user folder for VS Code; VS Code Insiders keeps its files under Code - Insiders).

In the JSON files, every other key stays as it is, including an env of the quiver entry, and the old file is saved next to it as <file>.quiver-backup. A file that is not valid JSON is reported and never overwritten. VS Code's mcp.json may contain comments: Quiver reads them, and writes the file without them after saving the .quiver-backup. When Codex already has a quiver entry, its env is kept too. Restart the assistant afterwards.

Every assistant but Claude Code gets the path of the binary itself, never the npm launcher: desktop apps do not see your shell's PATH, so they cannot find node.

Run quiver install again after you move the binary. A registration that points to another binary is replaced.

When it is done, quiver install prints one line per assistant on how always-on skills reach it, and quiver status lists the same. It says "hook" only when the hook is installed.

AssistantSkill list reaches the modelAlways-on skillsProject skills
Claude CodeYes, through the hookYes, through the hookYes, it starts the server in the project folder
CursorYes, through the hookYes, through the hookYes, it starts the server in the workspace folder
CodexYes, through the hookYes, through the hookYes, it starts the server in the working directory
AntigravityYes, through the hookYes, through the hookYes, it starts the server in the project folder
VS CodeYes, through the hookYes, through the hookYes, it sends the workspace as an MCP root
Claude DesktopNoNo; when you askOnly with QUIVER_PROJECT
Other clientsDepends on the clientDepends on the clientWhere it starts the server, or with QUIVER_PROJECT

See Always-on skills for how always-on skills reach each assistant.

A session-start hook adds the always-on skills in full, and the ID and description of every other skill served in the folder, to the context, so the model knows the skills from the first message. Claude Code also adds the server's short instructions to its system prompt. It starts the server in the folder you start Claude Code in, so project skills work.

Every served skill is also a prompt: run /quiver:<id>, such as /quiver:release-notes. Text after the command is passed to the skill as the task.

Cursor runs the session-start hook, so the skills reach the model from the first message, and starts the server in the workspace folder, so project skills work. Use Agent mode. Cursor's sub-agent event cannot add text, so Quiver sets up only the session-start hook.

Codex runs the session-start hook, so the skills reach the model without it looking for Quiver's tools. Codex's hooks are trusted automatically through codex app-server; if that fails, quiver install prints the "Review hooks" step. Quiver's read tools are marked read-only, so Codex runs them without asking.

Antigravity runs the session-start hook and starts the server in the project folder, so project skills work.

VS Code starts the server in your home folder and sends the workspace as an MCP root, which Quiver reads after startup to serve that project's skills. Quiver owns one hook file, ~/.copilot/hooks/quiver.json, which both of VS Code's harnesses read.

Claude Desktop runs Quiver's tools, but it drops the server's instructions and has no hook, so the model does not see the skills up front. A skill is used when you ask for Quiver's skills in the prompt, such as "check the quiver skills for this". quiver install says so when it sets it up.

Claude Desktop never starts the server in a project. To serve a project's skills there, set QUIVER_PROJECT in the entry (see below).

quiver mcp config prints the entry that starts this quiver, without changing anything:

{ "mcpServers": { "quiver": { "command": "/path/to/quiver", "args": ["mcp"] } } }

Add it to the assistant's MCP config. Whether the model sees which skills exist depends on whether the client passes MCP server instructions to the model. If it does not, ask for Quiver's skills in the prompt.

The server serves the project of the folder it is started in. An assistant that starts it somewhere else, such as your home folder, gets only the global skills, unless it sends its workspace as an MCP root (VS Code). Set QUIVER_PROJECT to a project folder in that assistant's MCP entry:

{
"mcpServers": {
"quiver": {
"command": "/path/to/quiver",
"args": ["mcp"],
"env": { "QUIVER_PROJECT": "/Users/me/code/app" }
}
}
}

quiver install keeps this env when it updates the entry.

Terminal window
quiver doctor

quiver doctor checks the entry of each installed assistant and the hooks of Claude Code, Codex, Cursor, Antigravity and VS Code. It reports a hook that is missing or runs another binary, a Codex hook that needs review, and an assistant with fewer hook commands than the text of your skills takes. The server logs to ~/.quiver/logs/mcp.log; a server started line names the folder and the project it serves. The hook logs to ~/.quiver/logs/hook.log.

Terminal window
quiver uninstall # from every assistant that has it
quiver uninstall claude-desktop # from one assistant

This removes the MCP server and Quiver's hooks. Your library and its skills are not touched.