-
licenseNot graded
qualityNot graded
maintenanceEnables kicking off deployed CrewAI workflows and inspecting their status and results.
-
Opus MCP Server
by Moenamatics
Related Servers
Alternatives to Opus MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects MCP clients such as Claude, Cursor, and VS Code to OpenCode's headless API so users can ask questions, implement features, monitor background jobs, respond to prompts and permissions, and review changes across multiple projects. It supports synchronous runs, fire-and-forget jobs with polling, and project-scoped workflows.24,321 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to submit and manage long-running Codex Desktop work asynchronously, with durable operation/workflow IDs, polling, approvals, Plan Mode workflows, retry safety, diagnostics, and final reports.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive Codex Desktop and codex-app-server through durable asynchronous operations for long-running tasks, with polling, approvals, Plan Mode workflows, retry-safe submission, and structured final reports.-
- FlicenseNot gradedqualityCmaintenanceEnables video generation through ComfyUI workflows, providing tools to list workflows, create and manage video jobs, upload assets, and retrieve results.-
- FlicenseNot gradedqualityAmaintenanceEnables users to submit long-running Codex Desktop tasks and workflows asynchronously, poll their status, handle approvals or plans, recover from restarts, and retrieve final reports and diagnostics.-
TDQS
A3.7/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity. Tools are organized around specific job lifecycle stages: initiation (initiate_job), execution (execute_job), status checking (get_job_status), result retrieval (get_job_results), audit logging (get_job_audit_log), workflow details (get_workflow_details), and file upload (generate_file_upload_url). There is no overlap in functionality.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is perfectly predictable: 'get_' for retrieval operations, 'initiate_' and 'execute_' for job control, and 'generate_' for URL creation. No deviations or mixed conventions exist.
Tool Count5/5
With 7 tools, the count is well-scoped for a job/workflow execution server. Each tool earns its place by covering essential aspects of the domain: workflow definition, job initiation, execution, status monitoring, result retrieval, audit logging, and file handling. This is neither too sparse nor bloated.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for job execution. It includes workflow discovery (get_workflow_details), job initiation (initiate_job), execution (execute_job), status tracking (get_job_status), result retrieval (get_job_results), audit logging (get_job_audit_log), and file upload support (generate_file_upload_url). There are no obvious gaps that would cause agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues