Skip to content

MCP tools and prompts

quiver mcp runs the MCP server on stdin and stdout. Assistants start it; you do not run it yourself. It serves the skills of the project in its working folder, or in $QUIVER_PROJECT when that is set, and logs to ~/.quiver/logs/mcp.log.

When a session starts, the server's instructions are short. They tell the assistant:

  • how to use the tools: get_skill, get_skill_file, list_skills and search_skills,
  • that new skills are saved with create_skill,
  • which skills are always-on, for an assistant without a session-start hook, and to load them with get_skill before the first reply,
  • to call list_skills before the first reply when the conversation has no <quiver-skills> block.

The skills themselves come from the session-start hook: the always-on skills in full, and the ID and description of the others. See Always-on skills.

ToolInputResult
list_skills—Every skill served here, project skills first: ID, name, whole description, global or project, and whether it is always-on.
get_skillidThe skill's instructions, its extra files and its folder.
get_skill_fileid, pathOne extra file of a skill, such as references/checklist.md. Large and binary files return their path instead.
create_skillname, description, body, scope (project or global), optional filesCreates a local skill, commits it and assigns it. In a folder that is not a project yet, project scope registers it.
update_skillid, any of description, body, files (an empty content deletes the file)Changes a local skill and commits it as update <name> (via MCP). Other frontmatter fields are kept. Source skills are read-only. It changes only skills served in the session's project, and never an always-on skill: change those with quiver edit.
search_skillsquerySearches the whole library, also skills not assigned here, and marks each match as assigned here (global or project) or not. The assistant may suggest an unassigned skill, but asks before using it.

Every served skill is also an MCP prompt, named by its ID. In Claude Code it appears as /quiver:<id>. Text after the command is passed to the skill as the task.

While a session runs, the server watches the library and the assignments. When they change, it sends prompts/list_changed, and list_skills returns the new list. The hook's text and the instructions do not change during a session.