findLABSCO SUMMARY
Your task app stays authoritative — this maps it rather than replacing it.
Caches and vector indexes are derived retrieval state, never a second record anybody has to edit, which is what keeps the team's existing workflow intact while the agent gains context between sessions. On top sits the knowledge-graph layer, for durable facts that no single task backend can hold: proposed by an agent from anywhere, ratified by a human, queried in one place.
What it is
An MCP server and CLI that maps your existing task app — TickTick, Obsidian, Notion, GitHub, Airtable, Beads or several at once — into a common task contract, retrieves relevant tasks and notes with provenance, and writes results back when the adapter supports it.
What you get
- Retrieval and CRUD over the active backend: find, get_task, create_task, set_task_intent, add_task_link, resolve_task_links
- Execution context and history: context_for_task, record_action, poll_task_events
- undo_write, for taking back something an agent wrote
- Adapters for TickTick, Obsidian, Taskmaster, Beads, Airtable, Google, Notion and GitHub — or several at once through the composite adapter
- Retrieval fused with RRF across keyword, native and optional dense branches, with result provenance retained
- A knowledge-graph layer for subject-predicate-object facts with provenance and temporal validity, exportable as JSON or Cypher
Requirements
npm install -g @reneza/ats-cli plus the adapter you want, for example @reneza/ats-adapter-ticktick. Select it with ats config use, then ats auth login. The MCP binary is ats-mcp and takes the adapter package name in ATS_ADAPTER; it speaks stdio, so any client that can launch one works.
Setup effort
Follow the published steps — npm install -g @reneza/ats-cli @reneza/ats-adapter-ticktick
USE CASES
01
Giving an agent memory that survives the session
Pull the context for the task you are on, from the system your team already updates.
02
Searching tasks, notes and issues in one query
One query across the configured backends, ranked together with provenance kept.
03
Writing a result back where the team will see it
Record the action against the task rather than leaving it in a chat log.
04
Taking back something an agent wrote
Undo the write instead of repairing the record by hand.
25 tools
Listed in project docs. Your client may show a different list.
get_taskcreate_taskupdate_taskset_task_intentpromote_explorationget_task_hierarchyset_task_hierarchyevaluate_task_hierarchyset_task_lifecycleget_task_securityset_task_securitycheck_task_accessadd_task_linkremove_task_linkresolve_task_linkstask_graphcontext_for_taskrecord_actionlist_actionsundo_writesnapshot_task_eventspoll_task_eventslist_pending_task_eventsacknowledge_task_eventsBEFORE YOU INSTALL
What to know first
Tools you get
25 tools named in the project's documentation.
Requires
- ats-mcp on PATH
- ATS_ADAPTER in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @reneza/ats-cli @reneza/ats-adapter-ticktick
ats config use ticktick
ats auth loginMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add ats -e ATS_ADAPTER=@reneza/ats-adapter-ticktick -- ats-mcpClaude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"ats": {
"command": "ats-mcp",
"env": {
"ATS_ADAPTER": "@reneza/ats-adapter-ticktick"
}
}
}
}OpenCode
OPENCODE · JSON
{
"mcp": {
"ats": {
"type": "local",
"command": [
"ats-mcp"
],
"environment": {
"ATS_ADAPTER": "@reneza/ats-adapter-ticktick"
},
"enabled": true
}
}
}Any MCP client — self-hosted
This address exists only after you deploy the project's Render blueprint (https://render.com/deploy?repo=https://github.com/renezander030/agentic-task-system) — local installs use stdio and have no URL. <YOUR_MCP_URL> is your deployed ats-mcp service's address. Have your client send the header Authorization: Bearer followed by the auto-generated ATS_MCP_TOKEN from the ats-mcp service's Environment tab. Set TICKTICK_ACCESS_TOKEN to read your real tasks.
ANY MCP CLIENT — SELF-HOSTED · URL
https://<YOUR_MCP_URL>/mcp
