A Model Context Protocol (MCP) server for Tana
If you already use Tana MCP, the tana mcp mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol (MCP) server for Tana.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Non — HTTP/HTTPS linkscreate_plain_node — Create simple text nodes with optional supertagscreate_formatted_node — Create nodes with rich formatting and inline referencescreate_reference_node — Create references to existing nodescreate_date_node — Create date nodes (supports various ISO 8601 formats)create_url_node — Create URL/link nodescreate_checkbox_node — Create checkbox/task nodescreate_file_node — Create file attachment nodes (base64 encoded)create_node_structure — Create complex nested node hierarchiescreate_supertag — Define new supertags in your schemacreate_field — Define new fields in your schemaadd_field_value — Add field values to existing nodestana-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: TANA_API_TOKEN, TANA_DEFAULT_TARGET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Tana MCP's toolset — Non, create_plain_node, create_formatted_node and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tim-mcdonnell; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Non | HTTP/HTTPS links |
| create_plain_node | Create simple text nodes with optional supertags |
| create_formatted_node | Create nodes with rich formatting and inline references |
| create_reference_node | Create references to existing nodes |
| create_date_node | Create date nodes (supports various ISO 8601 formats) |
| create_url_node | Create URL/link nodes |
| create_checkbox_node | Create checkbox/task nodes |
| create_file_node | Create file attachment nodes (base64 encoded) |
| create_node_structure | Create complex nested node hierarchies |
| create_supertag | Define new supertags in your schema |
| create_field | Define new fields in your schema |
| add_field_value | Add field values to existing nodes |
| set_node_name | Rename existing nodes (plain nodes only) |
| Limit | Value |
{
"mcpServers": {
"tana-mcp": {
"command": "npx",
"args": ["-y", "tana-mcp"],
"env": {
"TANA_API_TOKEN": "your-api-token-here",
"TANA_DEFAULT_TARGET": "INBOX"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TANA_API_TOKEN | Credential the server authenticates with. | Yes |
| TANA_DEFAULT_TARGET | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.