Vibeflow vs Next Devtools MCP
A side-by-side look at the Vibeflow and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
VibeflowDeveloper ToolsKanban for agentic development over MCP — annotate any UI element into a ticket with file and line.49FairAuth: no auth requiredVerdict: choose Vibeflow for developer tools work; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
VChoose Vibeflow when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You want tools like
list_tasks, get_task, get_project.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vibeflow | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 86/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 828 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 1 upvotes |
| Tools | 12 | 4 |
| Full listing | View Vibeflow | View Next Devtools MCP |
Tools & capabilities
Vibeflow tools 12
list_tasksList tasks with optional filters (root tasks only unless `children`)get_taskOne task by ID, with comments and filesget_projectThe resolved project this server is attached to — root, branch, modecreate_taskCreate a task, optionally annotated with a URL and selectorupdate_taskEdit a task: status, title, links, and the verification verdictclaim_next_taskClaim the highest-priority root task in `todo` as `in-progressadd_commentComment on a taskattach_fileAttach a file (base64); a `.md` satisfies the research-report gateexport_promptExport one or more tasks as a formatted LLM promptverify_taskRun visual verification for an annotated taskstart_kanbanStart the local Kanban board server and return its URLsget_integration_guideThe overlay/bookmarklet integration instructions
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Vibeflow
No confirmed install command for Vibeflow yet — follow the setup steps linked from its listing page rather than a guessed package name.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Vibeflow is categorized under Developer Tools and uses an install path we have not confirmed yet. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Vibeflow for developer tools work and Next Devtools MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vibeflow has no confirmed install command yet — follow its own setup instructions.
Vibeflow is listed as free. Auth: no auth required. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add vibeflow and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vibeflow has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 828 GitHub stars.