What it does
The server links an MCP-compatible AI coding agent to VibeMap. It loads project context, including features, user stories, acceptance criteria, personas, pages and the database schema, into the agent. As the agent works, it can update the VibeMap kanban board in real time. The server also works in reverse: pointed at an existing codebase, VibeMap's AI generates a structured set of features, user stories and acceptance criteria. The server exposes 55 tools under the vibemap_ prefix, covering projects, specs, kanban lifecycle, review and version control.
It suits teams that want an IDE agent to build against VibeMap specifications while the board reflects progress. The lifecycle tools let an agent claim criteria, report progress, submit work for review, ask the project owner questions when a spec is unclear, and propose spec changes rather than editing the spec directly. It is also relevant for someone who has existing code and wants it documented as VibeMap assets.
Setup requires Node.js 18 or later and a VibeMap account. A Personal Access Token is created in the VibeMap account settings and set as VIBEMAP_API_KEY. VIBEMAP_BASE_URL points to the VibeMap instance and defaults to a local address. The server is registered in the MCP settings of Claude Desktop, Cursor or Windsurf, and the client must be restarted after saving.
Limitations and requirements
Requires Node.js 18 or later, a VibeMap account and a Personal Access Token set as VIBEMAP_API_KEY. VIBEMAP_BASE_URL defaults to http://localhost:3000, so a hosted instance must be configured explicitly. The vibemap_agent tool is metered and uses VibeMap tokens. vibemap_resolve_review needs a CI-review token or a signed-in user. vibemap_update_kanban_status is deprecated in favour of the lifecycle tools.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.AshMet/vibemap-mcp
Load & create VibeMap product specs from your coding agent; sync build progress.
v2.8.1As shown on registry.modelcontextprotocol.io when we last read it