Agentic Task System (ATS)

io.github.renezander030Published by GitHub account renezander030v0.18.0Updated Oct 30, 2026

Persistent task context across TickTick, Notion, GitHub, Obsidian, Taskmaster and Beads

The publisher's own server: agentic.no

Overview

AI-generated overview

Local MCP server that exposes your existing task app (TickTick, Notion, GitHub, Obsidian, Beads) to an assistant for search, creation, updates and task…

What you can do
  • Search and read tasks: keyword retrieval fused with adapter signals, full task bodies, project lists, and semantically similar items.
  • Create and update tasks, and get paste-ready deep links back to the item in its native app.
  • Manage task structure: intent and completion conditions, hierarchy roles and parents, lifecycle states, and typed links with graph traversal.
  • Define and check task security: trust, scope, denials, approval boundaries, and audited access decisions.
  • Record and inspect an append-only agent action ledger, and snapshot, poll and acknowledge task-state events.
When to use it
Useful when an assistant should work against the task app you already use rather than a separate store, especially for multi-step agent work that needs persistent task context, explicit intent, hierarchy and access checks across sessions.
Requirements
Runs locally over stdio as an npm package, installed globally together with a storage adapter package. The adapter is chosen by the ATS_ADAPTER environment variable, a config file line, or a default TickTick adapter. The chosen backend (TickTick, Notion, GitHub, Obsidian, etc.) needs whatever credentials its adapter requires.
Before you install
Tools create, update and link tasks in your real task app, and write an action ledger and event spool. The security tools are only a decision point for cooperating clients and do not sandbox other tools. Adapters may need their own credentials for third-party services, and task data is sent to whichever backend the adapter targets.

Installation

In SourceWeft

  1. Open Agentic Task System (ATS) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@reneza/ats-mcp

Model Context Protocol server for the Agentic Task System.

It exposes the task app you already use to any MCP client (Claude Desktop, Cursor, …) as a small set of tools, backed by ATS's hybrid + RRF retrieval. It's storage-agnostic: it runs over any adapter that satisfies the ~6-method ATS contract. Generic adapters get keyword + native + RRF fusion for free; embedder-backed adapters (e.g. TickTick) get the full dense/sparse hybrid.

Tools

ToolWhat it does
findAvailable adapter signals plus Core keyword retrieval fused via RRF. Adapters with embeddings add dense+sparse hybrid. Pass explain: true for a per-result breakdown.
get_taskFetch one item (full body) by project id + task id.
list_projectsList projects / folders.
create_taskCreate an item — the agent→human write side of the two-way bus.
update_taskPartial update of an existing item.
similarSemantically similar items (embedder-backed adapters).
url_forPaste-ready deep link back to the item in its native app.
set_task_intentStore outcome, completion conditions, authority, constraints, and approval requirement.
promote_explorationCreate a committed execution item and link the source as evidence without copying its body.
get_task_hierarchy / set_task_hierarchyRead or assign exploration/goal/project/task role and one explicit parent.
evaluate_task_hierarchyCheck parent support, role ordering, cycles, lifecycle validity, and active explicit conflicts.
set_task_lifecycleSet active/archived/superseded state and validity windows.
get_task_security / set_task_securityRead or define task content trust, action/resource scope, denials, and approval boundaries.
check_task_accessRequire a reason, evaluate one scoped request, and append an allow/deny audit record.
add_task_linkAdd a typed relationship between two tasks.
remove_task_linkRemove one exact typed relationship.
task_graphTraverse incoming and outgoing typed relationships.
context_for_taskReturn valid deliberate context first, then retrieval discoveries, with provenance.
record_action / list_actionsWrite and inspect the append-only agent action ledger.
snapshot_task_events / poll_task_eventsEstablish and poll deterministic task-state events, durably staged before checkpoint advancement. Observation only; no agent execution.
list_pending_task_events / acknowledge_task_eventsRecover unacknowledged event envelopes and explicitly remove successfully consumed ids.

The security tools are a decision point for cooperating MCP clients. They do not sandbox tools outside ATS. The event tools emit state changes only. The local spool stores references and hashes, not task bodies. Consumers remain responsible for intent, lifecycle, access checks, and acknowledgement after successful handling.

Install & run

bash
npm install -g @reneza/ats-mcp @reneza/ats-adapter-ticktickats-mcp   # stdio server

The active adapter is resolved exactly like the CLI:

  1. ATS_ADAPTER env var, else
  2. ~/.config/ats/adapter (a single line with the adapter package name), else
  3. @reneza/ats-adapter-ticktick.

Wire it into Claude Desktop

json
{  "mcpServers": {    "ats": {      "command": "ats-mcp",      "env": { "ATS_ADAPTER": "@reneza/ats-adapter-ticktick" }    }  }}

Use a different store

Point it at any ATS adapter — a folder of markdown, Obsidian, Notion, your own:

bash
ATS_ADAPTER=@you/ats-adapter-obsidian ats-mcp

See the adapter contract — six storage methods plus authentication lifecycle hooks.


Source: packages/mcp/README.md at commit eb1da9d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v0.18.0LatestOct 8, 2026
  2. v0.17.0Oct 3, 2026
  3. v0.15.0Oct 2, 2026
  4. v0.9.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Agentic integrations