Feature request: MCP server for Vue Flow

[alexandre-meline]

Idea

Would it be possible to implement a Model Context Protocol (MCP) server for Vue Flow?

Context

MCP servers are becoming a standard way for AI coding agents (GitHub Copilot, Cursor, Windsurf, etc.) to access library-specific knowledge at development time. Several UI libraries have already shipped their own — for example Nuxt UI — and the developer experience improvement is significant.

What it could expose

An MCP server for Vue Flow could provide tools like:

• get-component — return the full API (props, events, slots, types) of a given component (VueFlow, MiniMap, Controls, Handle, Panel, …)
• list-components — list all available components with a short description
• get-composable — return the signature and usage of composables (useVueFlow, useNodesData, useHandleConnections, …)
• list-composables — list all composables
• get-edge-type / get-node-type — describe built-in node/edge types and how to create custom ones
• get-example — return a working code snippet for a specific use case (custom nodes, nested flows, drag & drop, etc.)
• search-by-category — find components/composables by category (layout, interaction, viewport, …)

Why it matters

Building with Vue Flow often involves wiring together composables, custom nodes/edges, event handlers and layout utilities. Having an MCP server would let AI agents:

1. Generate correct, up-to-date code instead of hallucinating outdated APIs
2. Discover the right composable/component for a task without leaving the editor
3. Reduce back-and-forth between docs and code

Prior art

Library	MCP server
Nuxt UI v3	@nuxt/ui-mcp
Tailwind CSS	@tailwindcss/mcp
Playwright	@playwright/mcp

Happy to help spec this out or contribute if there's interest!