agentic-task-system

data-ai MCP Server

MCP server + CLI that turns existing task systems into persistent agent context. Keyword/native retrieval by default; optional dense retrieval; RRF and provenance. Adapters: TickTick, Obsidian, Notion, GitHub, Airtable, Google, OKF, Taskmaster, Beads.

Verified
data-aidata-aigcp
6 views14 stars3 forksv0.10.0MIT

Why This Matters

Discovered via list:awesome-mcp-servers-punkpeye and last synced 1mo ago.

Verified
Source
list:awesome-mcp-servers-punkpeye
Stars
14
Last synced
1mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
19
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (19)

Approach

Authoritative record

none

keyword or the app's native search

Adapter

Authoritative source

ticktick

TickTick OpenAPI v1

obsidian

Local Markdown vault

okf

Open Knowledge Format Markdown bundle

taskmaster

Local `.taskmaster/tasks/tasks.json`

beads

Repository-local Beads via `bd --json`

airtable

Airtable REST API (table = project)

google

Google Sheets / Docs / Slides

notion

Notion databases + pages

github

GitHub issues + discussions

composite

Installed child backends

wishlist

Per-adapter auth and mapping live in each package's README. PRs welcome — scaffold and verify against the contract: ```bash ats adapter new linear # writes ats-adapter-linear/ (six stubs) ats adapter test ./ats-adapter-linear # pass/fail/skip per contract check ``` ## CLI surface ```bash # Lifecycle ats init

watch

pending

score

progress

Client

Where the config lives

Mode

Retrieval

json

yaml] ats url <id-or-title> # paste-ready note cross-reference ats links <project> <task> # resolve deep-links in a note body # Authoring ats create "<title>" [--content ..][--project <id>] ats update <project> <task> [--content ..][--title ..] # Agent execution context (portable across adapters) ats intent set <project> <task> --outcome ".." --done-when "a,b" ats promote <src-proj> <src-task> <target-proj> --outcome ".." --done-when "a,b" ats hierarchy set <project> <task> --kind task ats hierarchy evaluate <project> <task> ats lifecycle set <project> <task> --status active --valid-until 2026-12-31 ats link add <src-proj> <src-task> <dst-proj> <dst-task> --type decision ats graph <project> <task> ats context <project> <task> ats ledger record <project> <task> --action release.verified --advanced true ats security set <project> <task> --trust trusted --allow-actions read --allow-resources task:self ats security check <project> <task> --action read --resource task:self --reason "load context" ats events watch --json # NDJSON observations; never launches agents # Ops ats bench run ats bench score ats bench progress --json ats bench analyze-usage --days 7 npm run prove:intent npm run prove:taskmaster npm run prove:beads npm run prove:progress ``` ## Use it from any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf, OpenCode) [`@reneza/ats-mcp`](packages/mcp) exposes the active adapter as a tool set spanning retrieval, CRUD, and execution context (`find`, `get_task`, `create_task`, `set_task_intent`, `add_task_link`, `resolve_task_links`, `context_for_task`, `record_action`, `undo_write`, `poll_task_events`, and more). For Claude Code this provides persistent context between sessions without replacing the task system as the source of truth; optional caches and vector indexes remain derived retrieval state. ATS speaks MCP over **stdio**, so any client that can launch a stdio MCP server works. Only the config file and the wrapper key differ; the binary (`ats-mcp`) and its `ATS_ADAPTER` env are the same everywhere.