MCP Queue Orchestrator Service

Model Context Protocol server dedicated to the orchestration and sequential execution of discrete operational mandates within a FIFO structure.

Initial Setup (Client Perspective)

Prerequisites

• Node.js runtime environment, version 18 or newer (e.g., installed via brew install node).
• The Claude Desktop application (obtainable from https://claude.ai/desktop).

Configuration Procedure

1. Locate and open the configuration file for Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json

   Access path via the application menu: 1. Launch Claude Desktop. 2. Select 'Claude' in the macOS menu bar. 3. Choose 'Settings'. 4. Navigate to 'Developer' settings.

2. Integrate the following JSON snippet into your configuration structure under the tools section:

   { "tools": { "taskmanager": { "command": "npx", "args": ["-y", "@kazuph/mcp-taskmanager"] } } }

For Contributors (Development Workflow)

Requirements

• Node.js (version 18+).
• Claude Desktop.
• The tsx utility (installable via npm install -g tsx).

Source Integration

bash git clone https://github.com/kazuph/mcp-taskmanager.git cd mcp-taskmanager npm install npm run build

Development Configuration

1. Ensure Claude Desktop is operational.

2. Install tsx globally if absent: bash npm install -g tsx

Alternatively:

pnpm add -g tsx

1. Modify your primary Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json).

   Inject this configuration block to enable development mode execution:

   { "tools": { "taskmanager": { "args": ["tsx", "/path/to/mcp-taskmanager/index.ts"] } } }

Supported Operational Modalities

The Orchestrator component governs two primary stages of interaction:

Initialization Phase (Planning)

• Ingests a complete sequence of directives (an array of textual descriptions).
• Persists these directives internally within a managed sequential buffer.
• Outputs a procedural roadmap detailing the task inventory, assigned sequence identifiers, and the initial state of the buffer.

Iterative Phase (Execution)

• Delivers the subsequent pending directive from the buffer upon request.
• Features a mechanism for reporting the successful finalization of the directive.
• Automatically purges finalized directives from the buffer.
• Prepares the subsequent item for immediate retrieval.

Interface Parameters

• action: Specifies the operational mode: "plan", "execute", or "complete".
• tasks: Array of directive strings (mandatory for the "plan" action).
• taskId: Unique identifier for the directive (mandatory for the "complete" action).
• getNext: Boolean flag signaling the request for the next item in sequence (utilized with the "execute" action).

Usage Illustrations

typescript // Sequencing Initialization { action: "plan", tasks: ["Directive Alpha", "Directive Beta", "Directive Gamma"] }

// Sequence Advancement { action: "execute", getNext: true }

// Directive Finalization { action: "complete", taskId: "task-123" }