F
licenseNot graded
qualityD
maintenanceEnables AI assistants to query and manage Flowcore resources through a structured API.
176 npm
9
-
Parallel Works MCP Server
OfficialRelated Servers
Alternatives to Parallel Works MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with OpenProject's API v3 for comprehensive project management operations including work packages, projects, time tracking, users, and all other OpenProject features through natural language.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage projects through OpenProject's API, providing complete project management capabilities including work packages, tasks, and team collaboration features.-
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Automatisch workflow automation platform, allowing them to create, manage, and monitor workflows, connections, and executions through natural language commands.108 npm7MIT
- AlicenseNot gradedqualityDmaintenanceBridges AI assistants with OpenClaw Gateway, enabling them to chat with OpenClaw agents, manage sessions, and read agent workspace files.195 npmMIT
- AlicenseCqualityCmaintenanceEnables Claude and Claude Code to manage AACWorkflow tasks, agents, projects, squads, autopilots, and analytics through natural language.69MIT
TDQS
B3.3/5.0
Scored across 17 tools
Disambiguation5/5
Each tool targets a distinct resource: auth, organizations, groups, clusters, nodes, workflows, workflow YAML, storage types, sessions, allocations, Kubernetes, ML workspaces, and notifications. No two tools appear to serve the same purpose, and the resource-action pairs are clearly differentiated.
Naming Consistency3/5
The naming pattern is generally verb_noun, but there is inconsistency between 'get_' and 'list_' prefixes for essentially the same operation. For example, get_organizations and get_groups return lists, while list_clusters and list_workflows are used elsewhere. This mixed convention adds avoidable ambiguity.
Tool Count4/5
With 17 tools, the server covers a broad but reasonable domain of resources and actions. While slightly on the heavier side, each tool represents a distinct resource or operation, and the count aligns with the platform's diverse feature set without feeling excessive.
Completeness3/5
The tool surface is strong for read/listing operations and includes run_workflow as the primary action, but lacks create, update, or delete capabilities for most resources (e.g., creating a bucket, deleting a session, or stopping a workflow). This leaves the set incomplete for full lifecycle management, though it may suffice for monitoring and execution scenarios.
Maintenance
ActivityInactive
ResponsivenessNo issues