Skip to main content
Glama
Sign In
Task Orchard

Task Orchard

by its-glow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Task Orchard

A task and time management service for one person, used through an AI assistant over MCP.

You cultivate trees of tasks: big vague efforts, one-line reminders, recurring chores, things you want to do more of. In return the assistant helps you decide what to work on when you need it, using facts the server computes and what it has learned about how your work actually goes.

Status: scaffold and schema only. The server starts and serves one tool (get_guide). The task tools are specified in docs/SPEC.md and not yet built.

Documents

File

What it is

docs/SPEC.md

The feature specification: every operation, phase by phase, with acceptance tests.

IMPLEMENTATION_PLAN.md

The design and the reasoning behind it.

INITIAL_PLAN.md

The original idea.

CLAUDE.md

Working notes for whoever implements it.

Related MCP server: MCP Task Management Server

Quick start

Requires Python 3.12 or later and uv.

uv sync
uv run pytest
uv run task-orchard info

Configuration

Variable

Meaning

Default

TASK_ORCHARD_DB

Path to the SQLite database file.

~/.local/share/task-orchard/orchard.db

TASK_ORCHARD_TZ

Your timezone as an IANA name, such as Europe/London.

The system timezone, else UTC.

The database is created and migrated automatically on first start.

Connecting an MCP client

Task Orchard runs as a stdio MCP server. In your client, add a server whose command is:

uv run --directory /path/to/this/repo task-orchard

and set TASK_ORCHARD_TZ in that server's environment if your system timezone is not the one you want.

Trying it with demo data

TASK_ORCHARD_DB=/tmp/orchard-demo.db uv run task-orchard seed-demo

This fills a new database with a small realistic set of tasks (projects, blockers, an inbox, scheduled and flexible recurring tasks, history). Point your MCP client at the same TASK_ORCHARD_DB to explore it. The contents are described at the top of src/task_orchard/devtools/seed.py.

Available Tools

1 tool
get_guideGet GuideA

Read one of Task Orchard's guides: step-by-step instructions for a job.

Call with no name to list the guides. Call with a name to get its text, then follow it.

Inputs: name. Returns: object

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

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of misselection or overlapping purpose. The tool's role is unambiguous.

    Naming Consistency4/5

    The single name get_guide follows a clear verb_noun snake_case convention. Only one data point exists, so consistency across the set cannot be fully demonstrated.

    Tool Count3/5

    One tool is thin for a server whose domain is browsing and consuming multiple guides. It is workable but feels under-scoped for even a read-only surface.

    Completeness3/5

    Listing and fetching guide text are covered, but there is no search, categorization, or metadata operation to help an agent find the right guide among many. For a read-only guide service this is notable but not fatal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers