sol2flow MCP server
OfficialRelated Servers
Alternatives to sol2flow MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables compatible AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents through natural-language prompts.1,244 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and work on self-hosted project canvases, retrieving projects as JSON, Markdown outlines, Mermaid flowcharts or PNG images of the board, and, with a write-enabled token, adding sub-tasks and checking off work while the user watches. Access is scoped by tokens that are read-only by default and can be limited to particular projects.1 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage workspaces, projects, tasks, and AI agents, and to generate tools from any OpenAPI spec, through a hosted OAuth-secured endpoint or a local stdio package.1,244 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to securely read, update, and create tasks on ProjectFlow boards.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to connect to a Flow Master workspace and perform project, task, ticket, board, relationship, tag, and comment operations under the user's own account and permissions.3 npmISC
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.-
TDQS
Scored across 32 tools
Most tools have clearly distinct purposes, but update_task and move_task overlap in changing a task's list, and search and list_tasks both find tasks with different scopes. Descriptions help, but an agent could initially hesitate between them.
Nearly all tools follow a snake_case verb_noun pattern (list_tasks, create_board, update_task), with only minor exceptions like whoami and search as single-word commands. The convention is highly readable and predictable, though not perfectly uniform.
32 tools far exceeds the typical 3-15 range and crosses the rubric's 25+ threshold for 'too many'. While the domain is broad, several operations (especially timer controls) could be consolidated, making the set feel overly granular.
Core task lifecycle is well-covered (create, update, move, archive, comment, checklist, links, time), but boards, lists, and labels lack update/delete operations, and there is no way to invite people to a workspace or board. These notable gaps limit full administrative workflows.