Skip to main content
Glama
README.md
# MCP Orchestrator Server

[![Version](https://img.shields.io/badge/version-1.1.0-blue.svg)](CHANGELOG.md)
[![smithery badge](https://smithery.ai/badge/orchestrator-server)](https://smithery.ai/server/orchestrator-server)

The MCP Orchestrator Server provides task management and coordination capabilities across MCP enabled LLM instances like Claude Desktop or Cline. In simpler terms it allows for AI agents to create, share and execute tasks across instances 

<a href="https://glama.ai/mcp/servers/6hfxiaiuwg"><img width="380" height="200" src="https://glama.ai/mcp/servers/6hfxiaiuwg/badge" alt="Orchestrator Server MCP server" /></a>

## Features

### Version 1.1.0
- **Task Updates**: Modify pending tasks
- **Safe Deletion**: Delete tasks with dependency checks
- **Cycle Detection**: Prevent dependency cycles
- **Tool Listing**: Comprehensive tool documentation
- **Enhanced State Management**: Improved task state transitions

### Core Features
- Task creation with dependencies
- Multi-instance coordination
- Persistent task storage
- Dependency enforcement
- Task status tracking

## Installation

### Installing via Smithery

To install Orchestrator Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/orchestrator-server):

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

### Manual Installation
```bash
npm install
npm run build
```

## Usage

### Create a Task
```javascript
await create_task({
  id: 'setup',
  description: 'Initial setup'
});
```

### Get Next Task
```javascript
const task = await get_next_task({
  instance_id: 'worker-1'
});
```

### Complete Task
```javascript
await complete_task({
  task_id: 'setup',
  instance_id: 'worker-1',
  result: 'System initialized'
});
```

## Documentation

- [API Reference](docs/API.md)
- [Quick Start Guide](docs/QUICK_START.md)
- [Changelog](CHANGELOG.md)

## Roadmap

### Version 1.2.0
- Task priorities
- Timeouts
- Instance management

### Version 1.3.0
- Task groups
- Analytics
- Dashboard

## License
[MIT](LICENSE)

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 issues