Vibemap MCP

Name: Vibemap MCP
Author: AshMet

作者：AshMet版本 2.8.1i★ –i在你的电脑上运行

注册名称io.github.AshMet/vibemap-mcp

安装

概览

作者提供的说明（英文原文）

Load & create VibeMap product specs from your coding agent; sync build progress.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 68/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：VIBEMAP_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： VIBEMAP_API_KEY, VIBEMAP_BASE_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "vibemap": {
      "command": "npx",
      "args": [
        "-y",
        "@vibemap.ai/mcp-server"
      ],
      "env": {
        "VIBEMAP_API_KEY": "your-value",
        "VIBEMAP_BASE_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add vibemap --env VIBEMAP_API_KEY=your-value --env VIBEMAP_BASE_URL=your-value -- npx -y @vibemap.ai/mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibemap": {
      "command": "npx",
      "args": [
        "-y",
        "@vibemap.ai/mcp-server"
      ],
      "env": {
        "VIBEMAP_API_KEY": "your-value",
        "VIBEMAP_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "vibemap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@vibemap.ai/mcp-server"
      ],
      "env": {
        "VIBEMAP_API_KEY": "your-value",
        "VIBEMAP_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

VIBEMAP_API_KEY 机密必填 env
API key from vibemap.ai -> Account -> MCP (Pro plan)
VIBEMAP_BASE_URL env
Defaults to https://vibemap.ai

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 AshMet 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 4929 个服务器的 0%
发布到注册中心的时间比此分类中其他 4929 个服务器的 29% 更新
基础检查结果等于或优于此分类中其他 4929 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Vibemap MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：VIBEMAP_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.8.1）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者：github广泛使用★ 3.4万5天前更新

电脑或云端

安装

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者：wonderwhy-er广泛使用↓ 71万/周★ 1万17天前更新

在你的电脑上运行

安装

Cloudflare MCP

Cloudflare MCP servers

作者：cloudflare正在增长★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@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.

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 message box.

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
`VIBEMAP_API_KEY`	Your Personal Access Token (`vm_...`)	Required
`VIBEMAP_BASE_URL`	VibeMap instance URL	`http://localhost:3000`

Tools

The server exposes 55 tools via the vibemap_ prefix.

Projects & context

Tool	Description
`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 blueprint of the whole project (large; for scaffolds and audits, not for building a single ticket: use `vibemap_get_criterion_context` there)
`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

Personas & pages (spec authoring)

Tool	Description
`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

Conversational agent (hosted, metered)

Tool	Description
`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 the background (poll `get_generation_status`)

Features

Tool	Description
`vibemap_list_features`	List features with filtering
`vibemap_create_feature`	Create a new feature
`vibemap_update_feature`	Update feature fields or status (validates transitions). For spec authoring only: while building, use `vibemap_propose_spec_change`

User stories

Tool	Description
`vibemap_list_user_stories`	List stories by project or feature
`vibemap_create_user_story`	Create a user story
`vibemap_update_user_story`	Update story fields or status (validates transitions). For spec authoring only: while building, use `vibemap_propose_spec_change`

Acceptance criteria

Tool	Description
`vibemap_list_acceptance_criteria`	Fetch BDD criteria
`vibemap_create_acceptance_criterion`	Create a BDD acceptance criterion
`vibemap_update_acceptance_criterion`	Update a criterion's content (Given/When/Then, description). Status is not writable here: use the lifecycle tools below. For spec authoring only: while building, use `vibemap_propose_spec_change`

Kanban — board & agentic lifecycle

Tool	Description
`vibemap_get_kanban_board`	Get a real-time board view
`vibemap_get_execution_plan`	The build order: criteria grouped by sprint in dependency order, with state
`vibemap_get_next_ready_criterion`	Get the next criterion to work on, its story bundle, and a `reason` when nothing is claimable
`vibemap_claim_story`	Claim every claimable criterion of a story at once; returns a context pack for each
`vibemap_claim_criterion`	Claim a criterion (`ready` → `in_progress`)
`vibemap_get_criterion_context`	Everything needed to build one criterion in a few thousand tokens (use instead of the whole blueprint)
`vibemap_report_progress`	Heartbeat with the current `phase`, plus optional plan, files and test counts
`vibemap_submit_for_review`	Submit a criterion for review with the changed files and the named tests that prove it (→ `in_review`)
`vibemap_get_criterion_evidence`	Submission history of a criterion: files, tests and verdict per attempt
`vibemap_rework_criterion`	Send a criterion that failed review back to `ready` to build it again
`vibemap_resolve_review`	Resolve a review (`passed` / `failed`); needs a CI-review token or a signed-in user
`vibemap_block_criterion`	Block a criterion with a category and reason
`vibemap_ask_user`	Ask the project owner a question when the spec is unclear (blocks the criterion until answered)
`vibemap_get_answers`	Collect the answers to your questions
`vibemap_unblock_criterion`	Unblock a criterion with a resolution
`vibemap_propose_spec_change`	Propose a spec change for the owner to review when the code must differ; never edits the spec
`vibemap_list_kanban_events`	Kanban transition history (for incremental sync)
`vibemap_update_kanban_status`	⚠️ Deprecated — use the lifecycle tools above

Version control

Tool	Description
`vibemap_list_changesets`	List changesets (your writes + history) with op counts; `includeOps` for diffs, `sinceSeq` as a cursor
`vibemap_get_spec_delta`	What changed in the spec since a sequence number, and which criteria that affects
`vibemap_get_release_work_list`	A release's work grouped as new, modified and removed (with the code paths to delete)
`vibemap_get_release_diff`	A release's raw diff against its baseline
`vibemap_sync_changes`	Report changed paths since the last sync so VibeMap can flag spec drift

Codebase

Tool	Description
`vibemap_scan_codebase`	Walk a local directory
`vibemap_analyze_codebase`	Reverse-engineer a codebase into VibeMap assets
`vibemap_submit_code_map`	Submit a structural code map (nodes/edges) rendered on the project's Codebase tab
`vibemap_get_code_map`	Fetch the project's current code map (status, nodes/edges, sync anchor + drift)
`vibemap_get_generation_status`	Poll AI generation task status

Import an existing codebase

The structure is read on your machine with no model and no network call. What reaches VibeMap is the structural facts (table, column, policy and route definitions with their file paths) and the spec text your agent writes. File contents never leave your machine.

Tool	Description
`vibemap_extract_repo_facts`	Read the repository's tables, policies, routes and file clusters locally; sends nothing
`vibemap_import_facts`	Send the facts: VibeMap creates the schema, access rules and a page per route, each linked to its file
`vibemap_import_semantic`	Send the features, stories and criteria your agent wrote, each citing its source files
`vibemap_finalize_import`	Pass the imported criteria (unverified), lock MVP1 and open MVP2
`vibemap_resync`	Apply the structural changes at your current commit and flag the specs the changed files touch
`vibemap_resolve_drift`	Clear handled files, map units or criteria from the drift report
`vibemap_resolve_code_drift_proposal`	Apply or dismiss one staged code-drift proposal

Prompts (slash commands)

The server also exposes prompts — invocable workflows your IDE surfaces as slash commands (in Claude Code: /mcp__vibemap__ ). 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. Every prompt takes a projectId except new_project, which is the one that creates a project; the code-oriented ones also accept an optional localPath.

Prompt	Args	Description
`new_project`	—	Guided interview that creates a new VibeMap project. Start here
`author_spec`	`projectId`, `localPath?`	Author the full spec graph from your local codebase (bring-your-own-agent, code-first)
`author_idea`	`projectId`	Author the full spec graph from the project idea (bring-your-own-agent, idea-first)
`author_personas`	`projectId`	Stage 1 of 5 — author just the personas
`author_features`	`projectId`	Stage 2 of 5 — author just the features
`author_stories`	`projectId`	Stage 3 of 5 — author just the user stories
`author_criteria`	`projectId`	Stage 4 of 5 — author just the acceptance criteria
`author_pages`	`projectId`	Stage 5 of 5 — author just the pages
`author_schema`	`projectId`, `localPath?`	Author the database schema — tables, columns, relationships
`sync_changes`	`projectId`, `localPath?`	Detect and reconcile spec drift since the last sync
`code_map`	`projectId`, `localPath?`	Build and submit a structural code map
`load_context`	`projectId`	Load the project's spec context into your agent
`kanban`	`projectId`	Show the project's kanban board
`import`	`projectId`, `localPath?`	Import an existing codebase as a locked MVP1: extract locally, import the facts, write the spec per cluster, finalize
`resync`	`projectId`, `localPath?`	Bring an imported project up to date and stage drift proposals for review
`build_sprint`	`projectId`	Build the ready work test first while the board follows live; CI verifies, the agent never marks anything done
`release_next`	`projectId`	Build the next release: new and modified items, and delete what was removed

`gen_*` — run VibeMap's own generators

The author_* prompts above run on your model: your agent does the thinking and VibeMap just stores the result. The gen_* prompts are the other half — they run VibeMap's hosted generation pipelines, the same ones behind the app's /gen-… slash commands. They are metered (they draw down the project owner's VibeMap token budget) and asynchronous (you get a sessionId back and poll vibemap_get_generation_status).

Prompt	Args	Description
`gen_personas`	`projectId`	Generate personas — who you're building for
`gen_features`	`projectId`	Generate features — the set every story, page and table hangs off
`gen_stories`	`projectId`	Generate user stories from your features

| gen_criteria | projectId | Derive acceptance

只显示了开头部分；其余内容请在仓库中阅读