Load & create VibeMap product specs from your coding agent; sync build progress.
Most developer tooling work still happens through a UI a human drives. Vibemap MCP server moves it into the conversation instead. Load & create VibeMap product specs from your coding agent; sync build progress.
Generate your API key at vibemap.ai → Account → Developer → API Keys.
The server publishes 14 tools. What each one is for:
vibemap_list_projects — List all your projectsvibemap_create_project — Create a new project (use before analyze_codebase)vibemap_get_project_context — Load full project specs into agent contextvibemap_get_atomic_blueprint — Get the code-shaped atomic blueprint for LLM generationvibemap_list_access_rules — List table- and page-level access rules (with op_conditions) for RLS + authvibemap_get_page_source — Retrieve a page and its section source codevibemap_create_persona — Create a rich user persona (demographics, goals, pain points, …)vibemap_create_page — Create a page/screen in the project's page inventoryvibemap_create_schema — Persist the database schema (tables → columns → relationships) in one callvibemap_agent — Drive VibeMap's full conversational agent for one turn (same brain as the in-app chat). Metered — uses VibeMap tokens. Destructive turns return avibemap_list_features — List features with filteringvibemap_create_feature — Create a new featureBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: VIBEMAP_API_KEY, VIBEMAP_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vibemap's toolset — vibemap_list_projects, vibemap_create_project, vibemap_get_project_context and 11 more — is a fair guide to whether it matches your workflow. It is maintained by AshMet; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| vibemap_list_projects | List all your projects |
| vibemap_create_project | Create a new project (use before analyze_codebase) |
| vibemap_get_project_context | Load full project specs into agent context |
| vibemap_get_atomic_blueprint | Get the code-shaped atomic blueprint for LLM generation |
| vibemap_list_access_rules | List table- and page-level access rules (with op_conditions) for RLS + auth |
| vibemap_get_page_source | Retrieve a page and its section source code |
| vibemap_create_persona | Create a rich user persona (demographics, goals, pain points, …) |
| vibemap_create_page | Create a page/screen in the project's page inventory |
| vibemap_create_schema | Persist the database schema (tables → columns → relationships) in one call |
| vibemap_agent | 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 + operationId to approve in a second call; long generations run in th |
| vibemap_list_features | List features with filtering |
| vibemap_create_feature | Create a new feature |
| vibemap_update_feature | Update feature fields or status (validates transitions) |
| vibemap_list_user_stories | List stories by project or feature |
{
"mcpServers": {
"vibemap": {
"command": "npx",
"args": ["-y", "@vibemap.ai/mcp-server"],
"env": {
"VIBEMAP_API_KEY": "vm_your_token_here",
"VIBEMAP_BASE_URL": "https://vibemap.ai"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VIBEMAP_API_KEY | Credential the server authenticates with. | Yes |
| VIBEMAP_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.