A
licenseNot graded
qualityA
maintenanceEnables MCP clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language.
2,807 npm
MIT
Treeflow MCP Server
Related Servers
Alternatives to Treeflow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to manage workspaces, projects, tasks, and AI agents through natural language, with hosted or local connection options and OpenAPI-to-MCP tool generation.2,807 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects a workspace and project management platform to Claude, Cursor, VS Code, Windsurf, and other MCP clients, letting users list workspaces, create and manage projects and tasks, and build, train, and prompt AI agents. Also generates MCP tools from any OpenAPI spec.2,807 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to access and manage workspaces, projects, tasks, AI agents, automations, media, and Genesis app files through natural language.2,807 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, with a hosted OAuth server or a local stdio package. Also supports generating MCP tools from any OpenAPI spec.2,807 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude, ChatGPT, or any MCP client to a Five9 cloud contact center, exposing its admin and supervisor SOAP web services as JSON tools for natural-language management of campaigns, agents, DNC lists, call logs, and reports. It also builds complete IVR call flows from plain-English descriptions, validating, rendering, and deploying designer-shaped scripts plus AI-generated prompt audio.MIT
TDQS
B3.4/5.0
Scored across 45 tools
Disambiguation4/5
Tools are organized by resource type and action, so most are easy to tell apart. The only notable overlap is treeflow_get_tree vs treeflow_get_tree_data, but their descriptions clarify the different scopes. No other tools appear to serve the same purpose.
Naming Consistency5/5
All tools follow a consistent treeflow_ prefix with a predictable verb_noun pattern such as list, create, update, delete, get, configure, trigger, and simulate. Even the unusual use of 'leafs' is applied consistently across node-related tools. There is no mixing of naming conventions.
Tool Count2/5
With 45 tools, the server is well beyond the 25+ threshold and feels heavy for an agent to navigate. While the domain is broad, many operations could likely be consolidated or grouped more tightly. The sheer number of tools reduces overall coherence.
Completeness3/5
Core resources like branches, leafs, intents, entities, and message templates have full CRUD coverage, which is solid. However, there is no delete_tree, no delete_user, and fertilizers lack an update operation, leaving notable lifecycle gaps. Backup, training, conversation, and audit coverage is good but uneven across resources.
Maintenance
ActivityMaintained
ResponsivenessNo issues