@vibemap.ai/mcp-server
Connects your IDE agent to VibeMap for bidirectional synchronization: loading project specs into AI agents and reverse-engineering codebases into structured VibeMap assets.
Project & Context Management – List, create, and retrieve projects; load full specs (features, stories, personas, pages, DB schema, atomic blueprint, access rules); audit changesets.
Spec Authoring – Create user personas, pages, export page source, persist database schema.
Features, User Stories, Acceptance Criteria – Create, update, list, and filter by status; manage BDD-format criteria with scenario categories.
Kanban & Agentic Lifecycle – View board; claim, report progress, submit for review, resolve, block/unblock criteria; track kanban events.
Codebase Reverse Engineering – Scan directory; AI-powered reverse-engineering into features; submit/get structural code maps; sync changes to detect drift; poll generation status.
Slash Command Workflows (Prompts) – author_spec (code-first), author_idea (idea-first), sync_changes, code_map, load_context, kanban.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@vibemap.ai/mcp-serverload project specs for my app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@vibemap.ai/mcp-server
Connect your IDE agent to VibeMap via the Model Context Protocol. Load project specs into any MCP-compatible AI coding agent, or reverse-engineer an existing codebase back into structured VibeMap assets.
Quick Start
{
"mcpServers": {
"vibemap": {
"command": "npx",
"args": ["-y", "@vibemap.ai/mcp-server"],
"env": {
"VIBEMAP_API_KEY": "vm_your_token_here",
"VIBEMAP_BASE_URL": "https://vibemap.ai"
}
}
}
}Generate your API key at vibemap.ai → Account → Developer → API Keys.
Related MCP server: llmsproxy
What It Does
Outbound (VibeMap → IDE): Load your full project context — features, user stories, acceptance criteria, personas, pages, and DB schema — into your IDE agent. The agent builds to spec and updates your VibeMap kanban in real time as it works.
Inbound (IDE → VibeMap): Point the server at an existing codebase and VibeMap's AI will reverse-engineer it into a structured set of features, user stories, and acceptance criteria.
Requirements
Node.js ≥ 18
A VibeMap account
IDE Setup
Claude Desktop
Config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"vibemap": {
"command": "npx",
"args": ["-y", "@vibemap.ai/mcp-server"],
"env": {
"VIBEMAP_API_KEY": "vm_your_token_here",
"VIBEMAP_BASE_URL": "https://vibemap.ai"
}
}
}
}Fully restart Claude Desktop after saving. Confirm the 🔨 hammer icon appears in the chat input.
Cursor
Open Settings → MCP and add:
{
"vibemap": {
"command": "npx",
"args": ["-y", "@vibemap.ai/mcp-server"],
"env": {
"VIBEMAP_API_KEY": "vm_your_token_here",
"VIBEMAP_BASE_URL": "https://vibemap.ai"
}
}
}Windsurf
Same format as Cursor. Add to your Windsurf MCP settings file and restart.
Environment Variables
Variable | Description | Default |
| Your Personal Access Token ( | Required |
| VibeMap instance URL |
|
Tools
The server exposes 36 tools via the vibemap_ prefix.
Projects & context
Tool | Description |
| List all your projects |
| Create a new project (use before |
| Load full project specs into agent context |
| Get the code-shaped atomic blueprint for LLM generation |
| List table- and page-level access rules (with |
| Retrieve a page and its section source code |
Personas & pages (spec authoring)
Tool | Description |
| Create a rich user persona (demographics, goals, pain points, …) |
| Create a page/screen in the project's page inventory |
| Persist the database schema (tables → columns → relationships) in one call |
Conversational agent (Engine B — hosted, metered)
Tool | Description |
| Drive VibeMap's full conversational agent for one turn (same brain as the in-app chat). Metered — uses VibeMap tokens. Destructive turns return a plan + |
Features
Tool | Description |
| List features with filtering |
| Create a new feature |
| Update feature fields or status (validates transitions) |
User stories
Tool | Description |
| List stories by project or feature |
| Create a user story |
| Update story fields or status (validates transitions) |
Acceptance criteria
Tool | Description |
| Fetch BDD criteria |
| Create a BDD acceptance criterion |
| Update or mark criteria passed/failed (validates transitions) |
Kanban — board & agentic lifecycle
Tool | Description |
| Get a real-time board view |
| Get the highest-priority criterion ready to work on |
| Claim a criterion ( |
| Append a progress event to a criterion |
| Submit a criterion for review (→ |
| Resolve a review ( |
| Block a criterion with a category and reason |
| Unblock a criterion with a resolution |
| Kanban transition history (for incremental sync) |
| ⚠️ Deprecated — use the lifecycle tools above |
Version control
Tool | Description |
| List changesets (your writes + history) with op counts; |
| Report changed paths since the last sync so VibeMap can flag spec drift |
Codebase
Tool | Description |
| Walk a local directory |
| Reverse-engineer a codebase into VibeMap assets |
| Submit a structural code map (nodes/edges) rendered on the project's Codebase tab |
| Fetch the project's current code map (status, nodes/edges, sync anchor + drift) |
| Poll AI generation task status |
Prompts (slash commands)
The server also exposes prompts — invocable workflows your IDE surfaces as slash commands (in Claude Code: /mcp__vibemap__<name>). The body of each prompt is expanded from VibeMap's server at call time, so you invoke a workflow rather than paste a long instruction. Each takes a projectId; the code-oriented ones also accept an optional localPath.
Prompt | Args | Description |
|
| Author the full spec graph from your local codebase (bring-your-own-agent, code-first) |
|
| Author the full spec graph from the project idea (bring-your-own-agent, idea-first) |
|
| Detect and reconcile spec drift since the last sync |
|
| Build and submit a structural code map |
|
| Load the project's spec context into your agent |
|
| Show the project's kanban board |
Documentation
Full docs at vibemap.ai/docs/developer-docs/mcp-server/introduction
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server that connects AI coding tools to VibeCompass projects for reading context and writing decisions, conflicts, and session notes.1018MIT
- Alicense-qualityAmaintenanceConnects MCP clients (Claude Desktop, Cursor, Cline, Zed) to llmsproxy.ai, exposing chat, coding, and retrieval capabilities as MCP tools, resources, and prompts.12Apache 2.0
- Flicense-qualityDmaintenanceEnables LLM-powered code analysis, generation, debugging, and context management through MCP integration with IDEs like Cursor and Claude Desktop.
- Alicense-qualityDmaintenanceGives AI agents full access to IntelliJ IDE by running terminal commands, triggering builds, pushing notifications, and querying project context through a single MCP server with specialized plugins.81MIT
Related MCP Connectors
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AshMet/vibemap-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server