Because it speaks the Input API's node format, one call can lay down a project with its phases already nested and tagged, which is the part that is tedious by hand. Point TANA_DEFAULT_TARGET at INBOX and everything an agent writes lands in one place for you to process, the way you already process the rest of your inbox.
A server over Tana's Input API. That API is write-only, so this creates and extends nodes in your workspace rather than reading it back.
- Plain text nodes, with supertags attached at creation
- Formatted nodes carrying bold, italic, strikethrough and highlight, plus inline references to other nodes and inline dates
- Typed nodes for the cases Tana treats specially: dates in ISO 8601 forms, URLs, checkbox tasks, references to existing nodes, and base64 file attachments
- Whole nested hierarchies in one call, passed as a Tana node structure — a project with its phases, rather than a node at a time
- Schema work: new supertag and field definitions, and field values added to an existing node
- Renaming an existing plain node; Tana's API does not allow renaming checkbox nodes
- Four prompt templates — create-task, create-project, create-meeting-notes, create-knowledge-entry — and reference resources covering the Input API and the node types
A Tana workspace with API access and a token from Settings → API tokens, passed as TANA_API_TOKEN. Runs over stdio from npm as tana-mcp. TANA_DEFAULT_TARGET decides where nodes land — omit it for the Library root, set INBOX to route captures to your inbox, or give a node ID.
One command plus a key — npx -y tana-mcp, then supply credentials