What this covers
The whole project, not one repository. comfyui-mcp is several pieces that ship separately and version independently:
Items below are labelled by piece where it matters. Everything is planned as one
product even though it lands in four places.
How to read this
There are no dates on this page, and that’s deliberate. This project ships fast and reorders often — the RunPod arc jumped the queue in a single week. A roadmap with quarters on it would be wrong within days, and a wrong date is worse than no date: it turns a plan into a promise nobody made. So this page commits to order, not timing. “Next” means next in line, not next month. If something here matters to you, say so in Discord — what people actually do day to day moves things up this list far more reliably than the size of the request. The most useful section is probably the last one. Not planned says what we’ve decided against and why, so you can stop waiting for it.Shipped
Everything here works today and is covered by the docs.Building now
Actively in progress. These are the things most likely to move next.Next
Queued and specified, not started. Ordered.Under consideration
Wanted, but blocked on a design question rather than on effort. No commitment.Multi-user sessions
Letting someone else connect to your session and drive your machine — pair debugging a broken workflow, or a shared studio rig. Worth being precise about the blocker, because it isn’t the obvious one: the transport already exists. Pairing, socket fan-out and per-session auth were all built for phone-to-desktop mirroring, which is the same plumbing. What’s missing is a trust model. Who is allowed to drive? What can they see of your canvas, your history, your file system? How do you revoke access from someone mid-run? Those questions need answering before any of it gets built — shipping a half-designed answer on someone else’s GPU is how people get hurt.Not planned
Decided against, with the reasoning, so nobody waits on them. Not permanent — a good argument reopens any of these — but nothing here is queued.Dates and version-numbered milestones
See the top of this page. Order, not timing.Voice-only control (smart glasses, headsets)
Driving the desktop agent by voice from glasses comes up regularly, and the plumbing would mostly reuse the mirroring transport. The reason it isn’t queued is that a voice-only surface has no canvas. There’s no preview to glance at, no way to resolve “use the other LoRA” when two are loaded, and no visible undo when the agent does the wrong thing to your graph. Those are the actual problems, and adding a microphone doesn’t solve any of them. Until there’s an answer, this would ship as a demo that’s unpleasant to rely on.Smartwatch
Everything above applies, on a smaller screen with a tighter power budget. Nobody has yet described a job it does better than the phone already does.A hosted service that runs ComfyUI for you
This project is a local-first control plane. It connects to your ComfyUI — on your machine, your remote box, your pod, or Comfy Cloud — and it doesn’t want your files or your prompts. Running inference on your behalf is a different product with a different trust model, and it isn’t this one.How it got here
The arc so far, for context on where the next items sit. This is deliberately coarse — for what changed in a specific release, see the Changelog.Public releases begin at v0.2.0. There is no v0.0.1 or v0.1.x — the first
two weeks of work landed straight on
main before the package was published,
starting from the initial commit on 2026-02-15.
Two things that table won’t tell you. The pace is uneven on purpose — a
two-month lull in spring, then ~180 feature commits across June and July.
And the ordering has never been fixed in advance: RunPod and training both
jumped the queue because they turned out to matter more than what was
nominally next. That’s the main reason this page carries no dates.