Skip to content

MCP tools

VibeDoc's MCP server (http://localhost:<port>/api/mcp) has 52 tools. Every page here is generated from the tool definitions the server sends, so it matches the version you run.

ToolWhat it does
vibedoc_get_statusGet project status overview: active tasks, blockers, doc count, memory.
vibedoc_list_projectsEvery project VibeDoc knows (the projects hub): id, name, root folder and open tasks, marked archived / missing / this one.
vibedoc_get_frontendThe project's web frontend app (R057): dir, framework, start command, URL, whether it was detected or set in Settings, Playwright and auth state.
vibedoc_get_sessionsAgent and human sessions grouped from the activity log, newest first: who, when, tasks moved, docs changed, ADRs.
vibedoc_list_specsList the project's capability specs (docs/specs/<capability>.md): what each capability does today, as requirements with WHEN/THEN scenarios.
vibedoc_get_specRead one capability spec: the whole file, or only one requirement with its scenarios.
vibedoc_spec_contextGather what the project already says about one capability so you can draft its spec: matching epics (or the ones you pass) with their done tasks' Goal and Acceptance criteria, related docs, knowledge entries and the existing spec.
vibedoc_get_endpointLook up one HTTP endpoint in the project's OpenAPI 3.x spec (openapi.yaml / openapi.yml / openapi.json): parameters, request body and response shapes, with local $refs resolved.
vibedoc_read_docRead a doc file by name.
vibedoc_list_docsList the documentation grouped by section, with each doc's priority (P0 highest) when set: the root .md files and docs/, plans/, memory/.
vibedoc_set_doc_prioritySet a doc's priority (P0 highest … P3 lowest), or clear it with null.
vibedoc_search_docsFull-text search across all docs.
vibedoc_check_docsLint the project's docs (.md files): broken links, stale backticked paths, unparseable frontmatter, no H1 title, empty docs, orphan docs, capability spec structure, epic `## Spec changes` that wouldn't merge, and docs that may be outdated (they name a path a done task's commits renamed or deleted; the issue names the task and the new path).
vibedoc_write_docWrite or create a documentation file.
vibedoc_list_tasksList all tasks as a kanban board.
vibedoc_get_taskRead a specific task file including scope, criteria, and definition of done.
vibedoc_get_attachmentSee an image attached to a task (a screenshot the user pasted): returns the image itself.
vibedoc_get_evidenceRead a task's evidence doc: every checklist item with what its Playwright run proved (passed / failed with the error / missing / manual), screenshot file paths, the run's time, commit and video, and the history of kept runs.
vibedoc_verify_contextEverything needed to check a finished task against what was asked: its Goal, Scope and Acceptance criteria, the epic's Done when, the related capability spec, project conventions, and the diff of the commits that name the task (capped at ~2000 lines), plus how to report.
vibedoc_report_findingsRecord what a finished task gets wrong against what was asked: each finding names the acceptance criterion, scope item or rule it fails.
vibedoc_update_taskUpdate task status.
vibedoc_next_taskClaim the next ready task of an epic (deps done, not taken) and move it to in-progress.
vibedoc_log_decisionWrite a new Architecture Decision Record (ADR) when making a technical decision.
vibedoc_read_memoryRead MEMORY.md — the session handoff file.
vibedoc_update_memoryUpdate MEMORY.md with session summary.
vibedoc_memory_historyEarlier versions of MEMORY.md (a copy is saved before every write).
vibedoc_save_entrySave one long-lived fact (convention, gotcha, decision, preference) as its own entry.
vibedoc_import_memoryImport the developer's Claude Code memory for this project into knowledge entries.
vibedoc_export_memoryWrite the knowledge entries into a managed block in AGENTS.md (created if missing) and CLAUDE.md (if it exists), so Cursor, Codex and other agents see the same conventions.
vibedoc_recallSearch memory entries by topic or keyword.
vibedoc_get_entriesFetch full knowledge entries (body included) by id, after vibedoc_recall or the session-start index.
vibedoc_delete_entryDelete a knowledge entry that is wrong or no longer true.
vibedoc_create_docCreate a new doc from a template.
vibedoc_list_templatesList all doc templates with IDs, names, and default paths.
vibedoc_get_contextBundle multiple docs into a single context block.
vibedoc_propose_editPropose targeted edits to a doc for the user to review.
vibedoc_list_workersList this project's agent workers (R108: a worker runs an epic task by task in its own git worktree): id, epic, branch, base, phase (running, paused, wait-user, ended, stopped, failed), current task, the last line of its reply, commits ahead of its base and its dev server port.
vibedoc_propose_runPropose a worker run for the user to accept as a run card: a new worktree for the epic, or (mode "existing") sending it to the worker that already has the epic.
vibedoc_propose_planPropose a plan for the user to review: kind "breakdown" (tasks: pass epic for an existing epic, newEpic to create the epic with the tasks, or neither for loose tasks with no epic) or kind "roadmap" (new horizons and epics: horizons + epics; an epic's parent is an existing horizon id or a horizon key in this plan; epic body = one outcome sentence, a blank line, then **In scope:** / **Out of scope:** / **Done when:**).
vibedoc_ask_questionsAsk the user 1–4 multiple-choice questions, shown as a card in the chat UI (same shape as AskUserQuestion).
vibedoc_propose_toolkitShow the user a card with the vetted Claude Code plugins that fit this project (best fit first, each with a reason and whether it's installed).
vibedoc_get_planning_guideLoad the instructions for planning work from chat.
vibedoc_append_docAppend content to an existing doc file.
vibedoc_rename_docRename or move a doc file to a new path.
vibedoc_delete_docDelete a doc file.
vibedoc_get_file_mapGet a structured map of all documentation files with descriptions and last-modified dates.
vibedoc_read_registryRead docs/REGISTRY.md — file tree + annotations so you know which doc to open for any task.
vibedoc_rebuild_registryRegenerate docs/REGISTRY.md — refreshes the file tree, adds stub rows for new files, and preserves existing descriptions/keywords.
vibedoc_annotate_docAdd or update the description and keywords for one doc in the registry without a full rebuild.
vibedoc_get_roadmapGet the product roadmap: horizons (spine nodes, e.g.
vibedoc_create_roadmap_itemCreate a roadmap item (plans/roadmap/R*.md).
vibedoc_update_roadmap_itemUpdate fields of a roadmap item.