Vibeflow vs AI
A side-by-side look at the Vibeflow and AI 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 AI 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 AI when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vibeflow | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 12 | Not listed |
| Full listing | View Vibeflow | View AI |
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
AI tools
No tool names declared yet. Check the project README from the listing page.
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.
AI
{
"mcpServers": {
"contentrain-ai": {
"command": "npx",
"args": [
"-y",
"contentrain"
]
}
}
}
Frequently asked questions
Vibeflow is categorized under Developer Tools and uses an install path we have not confirmed yet. AI belongs to Developer Tools and uses a local stdio subprocess. Pick Vibeflow for developer tools work and AI 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. AI has no declared pricing — check the project's own site. 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 contentrain-ai 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. AI has 53/100 (Good) with 3 views, 0 installs and 6 GitHub stars.