Skip to main content
Glama

MCP 오케스트레이터 서버

버전 대장간 배지

MCP 오케스트레이터 서버는 Claude Desktop이나 Cline과 같은 MCP 지원 LLM 인스턴스 전반에 걸쳐 작업 관리 및 조정 기능을 제공합니다. 간단히 말해, AI 에이전트가 인스턴스 전반에 걸쳐 작업을 생성, 공유 및 실행할 수 있도록 지원합니다.

특징

버전 1.1.0

  • 작업 업데이트 : 보류 중인 작업 수정

  • 안전 삭제 : 종속성 검사를 통해 작업 삭제

  • 사이클 감지 : 종속성 사이클 방지

  • 도구 목록 : 포괄적인 도구 문서

  • 향상된 상태 관리 : 향상된 작업 상태 전환

핵심 기능

  • 종속성을 사용한 작업 생성

  • 다중 인스턴스 조정

  • 영구 작업 저장소

  • 종속성 적용

  • 작업 상태 추적

Related MCP server: task-orchestrator-mcp

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Orchestrator Server를 자동으로 설치하려면:

지엑스피1

수동 설치

npm install
npm run build

용법

작업 만들기

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

다음 작업 가져오기

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

작업 완료

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

선적 서류 비치

로드맵

버전 1.2.0

  • 작업 우선순위

  • 타임아웃

  • 인스턴스 관리

버전 1.3.0

  • 작업 그룹

  • 해석학

  • 계기반

특허

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…

    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

    Related MCP Connectors

    Related MCP Servers