add_field_value
Add a field value to an existing node in Tana
LABSCO SUMMARY
A capture channel into Tana that understands supertags, fields and nesting — not just plain text.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — npx -y tana-mcp, then supply credentials
USE CASES
01
Getting a thought into Tana without leaving the conversation
Create the node with its supertags already attached, routed to your inbox by default.
02
Turning a discussion into a project skeleton
Build the parent and its nested children in a single structured call instead of one node at a time.
03
Writing meeting notes that link to the people and dates involved
Create a formatted node with inline references to existing nodes and clickable dates in the text.
04
Tracking a to-do that came out of the conversation
Create the checkbox node, then fill the fields your workflow expects on it.
05
Extending the schema for a new kind of record
Define the supertag and the fields it carries, then create nodes that use them.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_checkbox_node
Create a checkbox/task node in Tana
create_date_node
Create a date node in Tana
create_field
Create a new field definition in Tana
create_file_node
Create a file attachment node in Tana
create_formatted_node
Create a node with rich formatted content including inline references and text styling. Use this when you need to link to other nodes or apply formatting.
create_node_structure
Create a complex node structure with nested children. Pass a JSON object conforming to the Tana API node format.
create_plain_node
Create a simple text node in Tana with optional supertags. For formatted content with bold, inline refs, etc., use create_formatted_node instead.
create_reference_node
Create a reference to an existing node in Tana
create_supertag
Create a new supertag definition in Tana
create_url_node
Create a URL/link node in Tana
set_node_name
Update the name of an existing node in Tana. Note: This only works on plain text nodes - checkbox/boolean nodes cannot be renamed via the API.
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. Every tool creates or writes: Tana's Input API is write-only, so no tool can read, list or search existing nodes. The 4 prompts and 4 resources are not tools.
Requires
- npx on PATH
- TANA_API_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y tana-mcpMCP Clients
Raycast
RAYCAST · JSON
{
"name": "Tana",
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tana-mcp"
],
"env": {
"TANA_API_TOKEN": "<YOUR_TANA_API_TOKEN>",
"TANA_DEFAULT_TARGET": "INBOX"
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add -s user \
-e TANA_API_TOKEN=<YOUR_TANA_API_TOKEN> \
-e TANA_DEFAULT_TARGET=INBOX \
tana-mcp \
npx -y tana-mcpClaude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"tana-mcp": {
"command": "npx",
"args": [
"-y",
"tana-mcp"
],
"env": {
"TANA_API_TOKEN": "<YOUR_TANA_API_TOKEN>",
"TANA_DEFAULT_TARGET": "INBOX"
}
}
}
}
