Section 3: MCP Server Guide
The Model Context Protocol (MCP) is an open standard that enables AI assistants (like Claude Desktop) to securely interact with local tools and data. The VibeMap MCP Server bridges the gap between your local development environment and the VibeMap AI-powered project management engine.
Why Use the MCP Server?
By connecting VibeMap directly to your IDE or AI assistant, you unlock a seamless "Round Trip" development workflow:
Reverse Engineering: Scan your existing code to automatically generate features, user stories, and acceptance criteria in VibeMap.
Deep Context: Your AI assistant gains immediate access to your project's "North Star" documentation, enabling it to write more accurate code that aligns with your business goals.
In-IDE Management: Update the status of requirements or view project summaries without leaving your terminal or code editor.
Code-to-Plan Sync: Ensure that what you're actually building matches what you've planned, highlighting drifts or missing requirements.
How it Works
The MCP Server acts as a stateless proxy. It receives tool calls from an MCP-compliant host (like Claude Desktop), authenticates with the VibeMap API using your Personal Access Token, and performs actions like listing projects, fetching context, or syncing data.
Key Capabilities
Read VibeMap Context: Pull your features and stories into your AI's working memory.
Write to VibeMap: Create or update project artifacts based on local code changes.
Codebase Scanning: Walk your local file structure to help the AI understand your project's physical implementation.
Last updated
Was this helpful?