Skip to content

ARCHITECTURE.md

Latest commit

 

History

History
44 lines (35 loc) · 1.07 KB

ARCHITECTURE.md

File metadata and controls

44 lines (35 loc) · 1.07 KB

Architecture

TaskFlow MCP is a local MCP server with a small, layered design.

flowchart TD
  A[MCP Client] -->|STDIO JSON-RPC| B[MCP Server]
  B --> C[Tools Layer]
  C --> D[Data Layer]
  C --> E[Prompt Templates]
Loading

Layers

  1. Server: MCP protocol handling and tool registration
  2. Tools: business logic for task planning, workflow, and research
  3. Data: task persistence and queries
  4. Prompts: templates used by planning and research tools

Data Model

Tasks are stored in a JSON document under the configured DATA_DIR. The schema is validated at runtime and includes fields for status, timestamps, dependencies, notes, and summaries.

classDiagram
  class TaskDocument {
    string version
    TaskItem[] tasks
  }
  class TaskItem {
    string id
    string name
    string description
    string status
    string createdAt
    string updatedAt
    string completedAt
  }
  TaskDocument "1" --> "*" TaskItem
Loading

Transport

The server uses STDIO transport. Clients call tools/list to discover tools and tools/call to execute them.