{"name":"io.github.AshMet/vibemap-mcp","slug":"ashmet-vibemap-mcp","title":null,"description":"Load & create VibeMap product specs from your coding agent; sync build progress.","url":"https://mcp.market/server/ashmet-vibemap-mcp","rating":null,"grade":"B","score":83,"certified":false,"status":"active","category":"ecommerce","tags":["ecommerce","ai"],"presence":{"score":22,"stars":0,"forks":0,"downloads_week":28,"last_push_at":"2026-09-20T06:34:44.000Z","license":"MIT"},"uptime":null,"claimed":false,"transport":"npm","callable_via_gateway":false,"default_price_micros":0,"repository":"https://github.com/AshMet/vibemap-mcp","website":null,"version":"2.8.1","remotes":[],"packages":[{"registryType":"npm","identifier":"@vibemap.ai/mcp-server","version":"2.8.1","transport":{"type":"stdio"},"environmentVariables":[{"description":"API key from vibemap.ai -> Account -> MCP (Pro plan)","isRequired":true,"isSecret":true,"name":"VIBEMAP_API_KEY"},{"description":"Defaults to https://vibemap.ai","name":"VIBEMAP_BASE_URL"}]}],"tools":[{"name":"vibemap_analyze_codebase","description":"Scan a local codebase and submit it to VibeMap for AI-powered reverse engineering. The server-side generation persists FEATURES from the code digest. It does NOT persist user stories or acceptance criteria — after the features task completes (poll vibemap_get_generation_status), create those yourself with vibemap_create_user_story and vibemap_create_acceptance_criterion, using your full codebase a","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_block_criterion","description":"Mark a criterion as blocked. Transitions any-active-status → blocked. Use this when external dependency, ambiguity, or environmental issue prevents progress.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_claim_criterion","description":"Atomically claim an acceptance criterion for implementation. Transitions ready → in_progress. Returns 409 (race) if another agent already claimed it.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_create_acceptance_criterion","description":"Create a new acceptance criterion for a user story in BDD format (Given/When/Then). Use this to flesh out what 'done' means for a story before or during implementation. You can call this multiple times to add multiple scenarios (happy path, error cases, edge cases) to the same story.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_feature","description":"Create a new feature in a VibeMap project. Use this when reverse-engineering a codebase to register discovered capabilities.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_page","description":"Create a page/screen in a VibeMap project's page inventory. Author pages after features, stories, and criteria to capture the app's screens and routes. Existing pages are visible via vibemap_get_project_context — enrich, don't duplicate.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_persona","description":"Create a user persona in a VibeMap project. Personas are the cast of users the spec is written for — author them FIRST, then reference each persona's role (userRole) when writing user stories. Match the depth VibeMap's own generator produces: fill the structured blocks so the persona is rich and semantically searchable, not just a name. Existing personas are visible via vibemap_get_project_context","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_project","description":"Create a new VibeMap project. Use this when starting from an existing codebase — create the project first, then call vibemap_analyze_codebase with the returned project ID.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_schema","description":"Persist a VibeMap project's database schema — tables, columns, and relationships — in one call. Author this LAST, after the rest of the spec exists, grounded on the spec (idea-first) or the codebase's models/migrations (code-first). One table per domain entity; give every table an `id` primary key and created_at/updated_at; set real Postgres column types + constraints; express foreign keys via eac","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_create_user_story","description":"Create a new user story inside a VibeMap feature. Provide the user role, action, and expected outcome.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_get_atomic_blueprint","description":"Retrieve a code-shaped atomic blueprint of a VibeMap project — relationships hydrated, Kanban metadata stripped, with synthesized interactions and entity state machines. Designed for LLM coders building the application end-to-end. Prefer this over vibemap_get_project_context when generating code; the blueprint omits PM narrative and process metadata to maximise signal-per-token.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_code_map","description":"Fetch the project's current code map (status draft|confirmed, nodes/edges, sync anchor incl. any drift report). Use before re-submitting to preserve the user's hidden-node curation where possible.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_generation_status","description":"Poll the status of a VibeMap AI generation task (e.g., reverse engineering or spec generation). Use the sessionId returned by vibemap_analyze_codebase.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_kanban_board","description":"Get a real-time kanban board view of a project grouped by status columns. Shows features with their stories nested underneath. Ideal for an IDE agent to understand what's planned, in progress, and done.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_next_ready_criterion","description":"Get the highest-priority acceptance criterion in `ready` status for the given project. Returns the criterion to work on next, or null if nothing is ready.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_page_source","description":"Retrieve a VibeMap page's generated source code so you can pull it straight into a repo. Returns the page's own source_code plus the source_code of each of its sections. Use this to export a generated page into your codebase instead of copy-pasting.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_get_project_context","description":"Retrieve the full context of a VibeMap project including features, user stories, personas, pages, and database schema. Use this before building a feature to understand all the specs.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_acceptance_criteria","description":"List acceptance criteria for a story, feature, or project. Returns BDD-formatted criteria (Given/When/Then) with status.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_access_rules","description":"List a VibeMap project's access-control rules: table-level rules (per persona/role, with can_select/insert/update/delete and structured op_conditions predicates like \"own rows only\") and page-level rules (can_view/create_content/edit/delete with predicates), plus an advisory reconciliation summary flagging page↔table drift. Use this to generate correct RLS policies and route/UI authorization — the","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_changesets","description":"List a VibeMap project's version-control changesets (most recent first) with a per-changeset op count. Every write you make through this server is wrapped in a changeset, so use this to see the changesets your own edits produced, audit who/what changed the project, or review recent edit history. Pass includeOps=true to inline each changeset's individual operations (entity_type, op, diff).","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_features","description":"List features for a VibeMap project. Supports filtering by status, priority, category, and search. Returns paginated results.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_kanban_events","description":"List kanban transition events for a project, newest first. Use `since` to fetch only events after a timestamp (for reconnect-backfill).","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_projects","description":"List all VibeMap projects for the authenticated user. Returns project IDs, names, descriptions, and status.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_list_user_stories","description":"List user stories for a project or feature. Filter by status, priority. Returns paginated results with full story detail.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_report_progress","description":"Append a progress event to the criterion timeline without changing its status. Used to surface intermediate work for visibility.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_resolve_review","description":"Resolve a criterion in review. Transitions in_review → passed | failed. NOTE: agents (env_token:agent) cannot self-resolve their own work — this tool requires a CI-scoped token (env_token:ci) or a session user.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_scan_codebase","description":"Scan a local directory and return a formatted tree view plus file statistics. Use this to explore and understand an existing codebase before syncing to VibeMap.","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_submit_code_map","description":"Submit a structural code map of the user's codebase to VibeMap (rendered on the project's Codebase tab). Build it yourself from your codebase access: one node per meaningful unit (page/route, API endpoint, data model, service, module, config), edges for imports/routes/reads/writes. Node kinds: page|api|model|service|module|config. Layers: ui|api|data|services|shared. Edge kinds: imports|routes|rea","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_submit_for_review","description":"Submit completed work for review. Transitions in_progress → in_review. Requires a git SHA and a diff URL as evidence.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_sync_changes","description":"Report codebase changes since the last sync so VibeMap can flag spec drift. Workflow: 1) call vibemap_get_code_map and read anchor.commitSha; 2) run `git diff --name-only <commitSha>..HEAD` (plus untracked files from `git status --porcelain`); 3) call this tool with the changed paths and your current HEAD sha. The response lists affected map units and features — update the stale specs with vibemap","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_unblock_criterion","description":"Unblock a criterion. Transitions blocked → prior_status (recorded when block was set; defaults to ready).","write_action":false,"price_micros":0,"input_schema":null},{"name":"vibemap_update_acceptance_criterion","description":"Update an acceptance criterion's status or content. Use status 'passed' when your code satisfies the criterion, 'failed' when it does not.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_update_feature","description":"Update an existing feature's fields or status in VibeMap.","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_update_kanban_status","description":"[DEPRECATED — use the typed transition tools (claim, report_progress, submit_for_review, resolve_review, block, unblock) instead. This tool will be removed in a future release.] Atomically advance or update the kanban status of a feature, user story, or acceptance criterion. Validates allowed state transitions and prevents invalid moves. Call this when you start or finish implementing something. F","write_action":true,"price_micros":0,"input_schema":null},{"name":"vibemap_update_user_story","description":"Update an existing user story's fields or status in VibeMap.","write_action":true,"price_micros":0,"input_schema":null}],"scan":{"score":83,"grade":"B","scanned_at":"2026-09-24T17:24:31.802Z","report":{"scannerVersion":"0.1.9","scannedAt":"2026-09-24T17:24:31.742Z","components":{"code":{"score":25,"max":25,"notes":["7 source files scanned"]},"reliability":{"score":-1,"max":20,"notes":["no gateway calls yet and no remote to probe"]},"poisoning":{"score":-1,"max":15,"notes":["tools not inspected (local package is not executed); not counted"]},"auth":{"score":6,"max":15,"notes":["static API keys via environment variables"]},"maintenance":{"score":15,"max":15,"notes":["last push 4 days ago"]},"identity":{"score":8,"max":10,"notes":["registry namespace matches repository owner","GitHub account older than a year"]}},"findings":[],"inputs":{"packages":[{"registryType":"npm","identifier":"@vibemap.ai/mcp-server","version":"2.8.1","found":true,"license":"MIT","hasInstallScripts":false,"dependencyCount":3,"publishedAt":"2026-07-30T05:13:42.998Z","repositoryUrl":"git+https://github.com/AshMet/vibemap-mcp.git","weeklyDownloads":28}],"repo":{"found":true,"owner":"AshMet","repo":"vibemap-mcp","archived":false,"pushedAt":"2026-09-20T06:34:44Z","stars":0,"forks":0,"openIssues":7,"ownerType":"User","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/5423635?v=4","ownerCreatedAt":"2013-09-10T02:56:03Z"},"icon":{"url":null,"source":"none"},"presence":{"stars":0,"forks":0,"downloadsWeek":28,"license":"MIT","lastPushAt":"2026-09-20T06:34:44.000Z","score":22}}}},"grade_history":[],"reviews":[]}