Skip to main content
Glama
Sign In
enesjakozh
MCP Orchestrator Server

MCP Orchestrator Server

by mokafari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Servidor del orquestador MCP

Versión insignia de herrería

El servidor MCP Orchestrator proporciona funciones de gestión y coordinación de tareas en instancias LLM compatibles con MCP, como Claude Desktop o Cline. En resumen, permite a los agentes de IA crear, compartir y ejecutar tareas en distintas instancias.

Características

Versión 1.1.0

  • Actualizaciones de tareas : modificar tareas pendientes

  • Eliminación segura : eliminar tareas con comprobaciones de dependencia

  • Detección de ciclos : previene ciclos de dependencia

  • Listado de herramientas : documentación completa de herramientas

  • Gestión de estados mejorada : transiciones de estados de tareas mejoradas

Características principales

  • Creación de tareas con dependencias

  • Coordinación de múltiples instancias

  • Almacenamiento de tareas persistentes

  • Cumplimiento de la dependencia

  • Seguimiento del estado de las tareas

Related MCP server: task-orchestrator-mcp

Instalación

Instalación mediante herrería

Para instalar Orchestrator Server para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install orchestrator-server --client claude

Instalación manual

npm install
npm run build

Uso

Crear una tarea

await create_task({
  id: 'setup',
  description: 'Initial setup'
});

Obtener la siguiente tarea

const task = await get_next_task({
  instance_id: 'worker-1'
});

Completar tarea

await complete_task({
  task_id: 'setup',
  instance_id: 'worker-1',
  result: 'System initialized'
});

Documentación

Hoja de ruta

Versión 1.2.0

  • Prioridades de tareas

  • Tiempos de espera

  • Gestión de instancias

Versión 1.3.0

  • Grupos de trabajo

  • Analítica

  • Panel

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Available Tools

7 tools
complete_taskC

Mark a task as completed

Inputs: task_id (required), instance_id (required), result (required).

create_taskC

Create a new task

Inputs: id (required), description (required), dependencies.

delete_taskA

Delete a task if it has no dependents

Inputs: task_id (required).

get_next_taskC

Get the next available task

Inputs: instance_id (required).

get_task_detailsC

Get details of a specific task

Inputs: task_id (required).

get_task_statusC

Get status of all tasks

Inputs: no named parameters.

update_taskC

Update an existing pending task

Inputs: task_id (required), description, dependencies.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools target specific actions like creating, updating, deleting, completing, and retrieving tasks, with clear boundaries between them. For example, get_task_details and get_task_status serve different retrieval functions, and delete_task has a specific condition that distinguishes it.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern throughout, such as create_task, update_task, and get_task_details. There are no deviations in naming conventions, making the set predictable and easy to understand for an agent.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a task management server, covering essential CRUD operations and status checks. Each tool earns its place by addressing a specific aspect of task handling, without being overly sparse or bloated.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for task management, including creation, retrieval, updating, deletion, completion, and status monitoring. There are no obvious gaps, and agents can perform all necessary operations without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches