VibeMap developer documentation

Name: VibeMap
Availability: InStock
Author: VibeMap

Welcome. This is the developer documentation for VibeMap — written for the people using VibeMap to plan and build their products.

If you've never used VibeMap before, start with 1.1 — What is VibeMap?.

If you just want to plug VibeMap into your IDE agent and go, skip to 1.4 — Connect your AI coding agent.

Who this is for

Solo founders, indie hackers, PMs, and engineers using VibeMap to draft and ship product specs.
Anyone wiring up an AI coding agent (Cursor, Claude Code, Windsurf, VS Code Copilot) to a structured backlog.
Builders of custom integrations who want to drive VibeMap from scripts, CI, or their own UIs.

Section	What it covers
1 — Getting started	Sign up, your first project, connecting your AI agent
2 — Core concepts	How VibeMap works, the entity hierarchy, what you control vs the AI
3 — AI generation	What gets generated, model options, tips for better output
4 — API reference	REST API for CRUD and generation
5 — MCP server	The MCP integration your IDE agent talks to
6 — Kanban tracker	The live board your agent works against — user guide + API reference
7 — Plan & sprints	Sprint planning (Pro+) — user guide + API reference
8 — Tips & best practices	Common pitfalls and how to get better output
9 — App Builder	🚧 Admin preview — architecture of the compile → fill → verify → deploy build pipeline (for contributors)

Sign up at vibemap.ai and verify your email.
Create your first project with a one-paragraph prompt describing what you're building.
Review and approve the generated features, user stories, and acceptance criteria.
(Pro+) Plan sprints from the Plan tab.
Install the MCP server in your IDE — see Connect your AI agent.
Ask your agent "What should I work on next?" and you're off.

Found a gap in these docs? Let us know in the in-app feedback form — every gap is a chance to make this clearer.