SOLVE-IT Workflow MCP Server
Related Servers
Alternatives to SOLVE-IT Workflow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceTurns messy operational documents, SOPs, incident playbooks, spreadsheets, and business communications into faithful, source-grounded visual workflows directly inside Claude Desktop, Cursor, Zed, Windsurf, or any MCP-compatible agent. It also supports revising existing workflow graphs while preserving citation integrity and retrieving stored visual artifacts by ID.9ISC
- AlicenseAqualityDmaintenanceEnables AI agents to manage ComfyUI workflows using a human-readable Domain Specific Language (DSL), with automatic conversion to/from JSON format. Supports workflow creation, validation, execution, and monitoring through natural language interactions.163MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to generate images via ComfyUI from natural language requests, automating workflow construction and execution.1MIT
- AlicenseAqualityFmaintenanceEnables Claude Desktop to interact with local ComfyUI installations for AI-powered image generation, including workflow management, model selection, real-time monitoring, and custom workflow execution through natural language.1412,397 npm18MIT
- AlicenseNot gradedqualityBmaintenanceEnables building and running visual workflows conversationally inside Claude, orchestrating your existing connector tools step-by-step without storing credentials or owning integrations.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to create and modify SOLIDWORKS parts, assemblies, sheet metal, weldments, drawings, and bills of materials from natural-language requests, run strength simulations, and receive model views and stress maps as images.1AGPL 3.0
TDQS
Scored across 7 tools
Each tool targets a distinct lifecycle action: status (server readiness), find_techniques (lookup), create, update, inspect, validate, and compile. The only mild overlap is validate vs. compile, since compile also surfaces validation errors, but the descriptions clearly distinguish structural checking from weakness/mitigation reporting.
All tools share a predictable 'workflow_' prefix, and most follow a verb_noun pattern (find_techniques, create, update, inspect, validate, compile). workflow_status is a noun rather than a verb, a minor deviation but still readable and unambiguous.
Seven tools is well-scoped for a workflow authoring domain, covering discovery, CRUD-ish editing, inspection, validation, and compilation without redundancy or bloat.
The surface covers the full authoring loop: find techniques, create, update (add/remove nodes and edges), inspect, validate, and compile. A dedicated delete/remove-workflow tool is missing, but node/edge removal is handled inside update, so agents can work around it.