Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Withvibe Roadmap

by withvibeversion 2.0.0i★ 0i–
Registry nameio.github.withvibe/withvibe-roadmap

How to install

What it does

Per-env roadmap board for WithVibe — an MCP server the orchestrator drives to plan and track work.

  • Connects –
  • Account or key No key needed
  • Category Other

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect Withvibe Roadmap yet

The maker has not listed install details in the MCP Registry yet

ChatGPT cannot connect Withvibe Roadmap yet

The maker has not listed install details in the MCP Registry yet

What you can do instead

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Withvibe Roadmap yet

The maker has not listed install details in the MCP Registry yet

Cursor cannot connect Withvibe Roadmap yet

The maker has not listed install details in the MCP Registry yet

VS Code cannot connect Withvibe Roadmap yet

The maker has not listed install details in the MCP Registry yet

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Withvibe Roadmap💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
–
Latest versioni
2.0.0
Categoryi
Other
Published to registryi
Jun 9, 2026
Code last changedi
Jun 9, 2026
Maker
withvibe
Registry status
Active

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 15, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account withvibe, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 5 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

What we check → · JSON

Makers: ask for a re-check or report wrong info

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 19857 servers in this category
  • Published to the registry more recently than 9% of the other 19857 servers in this category
  • Basic checks equal to or better than 100% of the other 19857 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Withvibe Roadmap safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 5 months ago, and the latest version (2.0.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

by koala73Widely used★ 90.6KUpdated yesterday

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 26 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
  • World Monitor — Runs in the cloud, nothing to install · No key needed
  • openstatus — Runs in the cloud, nothing to install · No key needed
  • Oh My Posh Validator — Runs in the cloud, nothing to install · No key needed
  • Strata — Runs in the cloud, nothing to install · No key needed
  • Jitsu — Runs in the cloud, nothing to install · No key needed

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

WithVibe Roadmap Plugin

A per-env implementation roadmap board for WithVibe — Postgres-backed, with an MCP server the AI orchestrator drives directly.

Multi-phase features drift. Plans change mid-flight. After a few sessions you lose track of what shipped, what's pending, and which step you're actually on. This plugin gives the AI a structured place to keep that state — and the user a live view of it.

Feature: Auth rewrite                          ▓▓▓▓░░░░░░ 4/11 tasks

you are here → API layer › Wire DTO validation

[x] Phase 1: Schema (done) [~] Phase 2: API layer (in progress) [x] Endpoint scaffolding [x] Auth guard [~] Wire DTO validation ← active [ ] Error envelope [ ] Phase 3: Web [ ] Phase 4: QA

— Plan changes — 2026-05-28 AI added Phase 4 (QA) — reason: integration tests not in original scope 2026-05-29 user removed "Add caching" — reason: deferred to follow-up

What's in the box

  • Hierarchical roadmap — feature → phase → task, with pending / in_progress / done / blocked / deferred / canceled statuses.
  • "You are here" marker — exactly one task is active at a time; the banner is the recovery anchor when you context-switch back.
  • Plan-change log — every add/remove/rename/status-change records an actor (ai or user) and an optional reason. The trail makes drift visible.
  • MCP tools the AI orchestrator uses without prompting: propose_plan, set_active_task, complete_task, add_note, update_task, log_change, …
  • Live UI — htmx-based, polls a tiny version endpoint so the iframe updates within ~4s of any AI change without scroll jumps.
  • Persistent — uses WithVibe's shared-postgres plugin storage, so state survives container restarts.

Architecture

manifest.yaml ──→ WithVibe spawns one container per env

↓ server.js (express) ├── /health platform health probe ├── /mcp AI orchestrator's MCP endpoint ─→ mcp.js ├── /ui dark-themed htmx UI ─→ ui.js └── /ui/version cheap freshness check (drives live updates) ↓ db.js (pg) ↓ shared-postgres per-env schema plan / phase / task / plan_event

  • Scope: `env` — one container per (env, plugin). Each env gets its own roadmap, its own Postgres schema, its own port.
  • Storage: shared-postgres — the platform provisions a dedicated role + schema in the withvibe_plugins database and injects DATABASE_URL + PGSCHEMA at spawn. The plugin role can't reach the main withvibe DB.
  • State surface: four tables in db.js — plan (singleton), phase, task, plan_event (change log).

MCP tools

All tools return the full updated plan in the trailing text so the AI never holds stale state.

ToolPurpose
get_planRead the full roadmap + active marker + last 20 events.
propose_planReplace the whole roadmap (initial planning or a major re-plan).
add_phase / add_taskAppend work mid-flight; reason recorded.
set_active_taskMark the "you are here" anchor before starting work.
complete_taskMark done with a 1-line outcome; auto-closes the phase if every task is done.
update_task / update_phaseEdit title/description/status (blocked, deferred, canceled) with reason.
add_noteAppend a markdown note — decisions, things tried, references.
log_changeNarrate a plan-level decision without mutating data.

See mcp.js for the full schemas.

Build

docker build -t local/roadmap:2.0 .

The image is multi-arch-friendly via Node 20 Alpine, ~150 MB, no native build steps.

Install in WithVibe

  1. Workspace admin → Plugins → Install plugin.
  2. Paste the contents of manifest.yaml into the editor.
  3. The platform pulls / locates the image and registers the plugin.
  4. Open any env → the Roadmap tab appears in the plugin panel.

To update after rebuilding the image, hit Update on the plugin row in the admin list — running instances are stopped so the next env start picks up the new image.

Manifest

The manifest is the entire install input. The fields that matter for this plugin:

id: withvibe.roadmap          # URL + tool prefix; reverse-DNS-ish

name: Roadmap # display name in the env's plugin panel version: 2.0.0 icon: list-todo # Lucide icon image: local/roadmap:2.0 # OCI ref

scope: env # one container per env storage: kind: shared-postgres # platform-managed Postgres role + schema

ui: path: /ui # iframe entry point websocket: false

mcp: enabled: true path: /mcp # MCP endpoint the AI auto-discovers

Local development

# Build

docker build -t local/roadmap:2.0 .

Run standalone (requires a Postgres reachable via DATABASE_URL)

docker run --rm -p 8080:8080 \ -e DATABASE_URL="postgres://user:pass@host.docker.internal:5432/withvibe_plugins" \ -e PGSCHEMA="roadmap_dev" \ local/roadmap:2.0

Then open http://localhost:8080/ui

When developing against a real WithVibe install, hit Update in the admin Plugins page after each rebuild — that stops running instances so the next env start picks up the new image.

Repository layout

manifest.yaml   WithVibe plugin manifest

Dockerfile builds the runtime image package.json npm deps (express, pg, @modelcontextprotocol/sdk, zod) server.js express entry, HTTP + MCP routes db.js pg pool, schema init, query helpers mcp.js MCP tool registrations ui.js htmx UI rendering + dark-themed CSS

Contributing

Issues and PRs welcome. Keep changes focused and document the *why* in commits.

License

Apache License 2.0. See NOTICE for attribution.