Tana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TANA_API_TOKEN | Yes | Your Tana API token (generated from Tana Settings > API Tokens) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-task | Create a task node in Tana with optional due date and tags |
| create-project | Create a project structure in Tana with goals and milestones |
| create-meeting-notes | Create structured meeting notes in Tana |
| create-knowledge-entry | Create a knowledge base entry in Tana |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Tana API Documentation | Overview of Tana Input API capabilities and usage |
| Tana Node Types Reference | Detailed information about all supported node types |
| Common Usage Examples | Example patterns for common Tana operations |
| Server Information | Current server status and configuration |
TDQS
Scored across 11 tools
The tools have overlapping purposes with unclear boundaries, as multiple 'create_' tools (e.g., create_checkbox_node, create_plain_node, create_file_node) seem to create different node types without clear distinctions in their descriptions. While they target different node types, the lack of descriptions makes it ambiguous when to use one over another, especially for similar-sounding tools like create_field and create_field_node.
The tool names follow a highly consistent verb_noun pattern throughout, with all tools using 'create_' or 'set_' prefixes followed by descriptive nouns (e.g., create_checkbox_node, set_node_name). There are no deviations in naming conventions, making the set predictable and readable.
With 11 tools, the count is reasonable for a server focused on node creation and management in Tana. It is well-scoped, though slightly on the higher side, as each tool appears to serve a specific node type or action, earning its place without being excessive.
The tool surface is significantly incomplete for node management, as it only includes creation and naming tools (e.g., create_* and set_node_name) with no obvious operations for reading, updating, or deleting nodes. This lack of CRUD coverage will likely cause agent failures when trying to perform full lifecycle management.