Skip to main content
Glama
Tana MCP Server

Tana MCP Server

Tana MCP 服务器

连接到Tana 的输入 API 的模型上下文协议 (MCP)服务器,允许大型语言模型 (LLM) 和其他 MCP 客户端在 Tana 工作区中创建和操作数据。

特征

该 MCP 服务器完全实现了 Tana 输入 API 的所有功能:

Available Tools

11 tools
create_checkbox_nodeD

Inputs: name (required), checked (required), targetNodeId, description, +1 more.

create_date_nodeD

Inputs: date (required), targetNodeId, description, supertags.

create_fieldD

Inputs: name (required), targetNodeId, description.

create_field_nodeD

Inputs: attributeId (required), targetNodeId, children.

create_file_nodeD

Inputs: fileData (required), filename (required), contentType (required), targetNodeId, +2 more.

create_node_structureD

Inputs: node (required), targetNodeId.

create_plain_nodeD

Inputs: name (required), targetNodeId, description, supertags.

create_reference_nodeD

Inputs: referenceId (required), targetNodeId.

create_supertagD

Inputs: name (required), targetNodeId, description.

create_url_nodeD

Inputs: url (required), targetNodeId, description, supertags.

set_node_nameD

Inputs: nodeId (required), newName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.7/5.0

    Scored across 11 tools

    Disambiguation2/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers