Opus MCP Server

Related Servers

Alternatives to Opus MCP Server

No user-submitted related servers found.

Related Servers

CrewAI Enterprise MCP Server
danielfsbarreto
-
license
Not graded
quality
Not graded
maintenance
Enables kicking off deployed CrewAI workflows and inspecting their status and results.
Updated a year ago (2025-10-07 23:06 UTC)
-
Independent Video Generator
Image & Video Processing AI & Machine Learning
yt0912iii
F
license
Not graded
quality
C
maintenance
Enables video generation through ComfyUI workflows, providing tools to list workflows, create and manage video jobs, upload assets, and retrieve results.
Updated a month ago (2026-08-25 09:55 UTC)
-
Procesio MCP Server
App Automation Workplace & Productivity Developer Tools
serenichron
A
license
B
quality
D
maintenance
Enables interaction with the Procesio automation platform to list, view, and manage workflows. It allows users to launch process instances and monitor their status through MCP-compatible clients.
Updated a year ago (2025-06-30 10:17 UTC)
1
2
Apache 2.0
Orchestra MCP Serverofficial
Data Platforms Observability
orchestra-hq
F
license
Not graded
quality
A
maintenance
Enables interaction with the Orchestra API for managing pipelines, runs, logs, and artifacts through natural language.
Updated 2 days ago (2026-09-18 17:40 UTC)
-
Oomol Connect MCP Serverofficial
Multimedia Processing Audio Processing App Automation
oomol-lab
A
license
Not graded
quality
D
maintenance
Enables integration with Oomol Connect for executing tasks, managing blocks and packages, and uploading files. Supports task execution with real-time progress monitoring and intelligent polling across audio, video, and other processing workflows.
Updated 9 months ago (2025-12-20 05:35 UTC)
11 npm
MIT
zadig-mcp
CI/CD & DevOps Developer Tools
Deraiven
F
license
C
quality
B
maintenance
Enables management of Zadig CI/CD workflows, builds, services, environments, and webhooks through the Zadig OpenAPI.
Updated 20 days ago (2026-09-01 04:47 UTC)
49
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored 2026-04-18 08:00 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.