2,500+ MCP servers ready to use
Vinkius

Tana MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Tana through Vinkius, pass the Edge URL in the `mcps` parameter and every Tana tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Tana Specialist",
    goal="Help users interact with Tana effectively",
    backstory=(
        "You are an expert at leveraging Tana tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Tana "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Tana
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Tana MCP Server

Translate your AI conversation into structured personal knowledge management seamlessly with the Tana MCP connector. Evolve your LLM into a dedicated ontological architect capable of pushing rich, contextual data fragments straight into your workspace. Bypass tedious manual entry by programming your assistant to dynamically categorize thoughts, mint native ontological classes (Supertags), and instantiate multi-level hierarchies inside your Tana graph while maintaining maximum focus in your local environment.

When paired with CrewAI, Tana becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Tana tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Node Structuring — Swiftly inject clean data fragments anywhere by defining paths invoking add_node or securely drop ideations asynchronously into your capture zone utilizing add_to_inbox.
  • Ontology & Metadata — Formalize data classifications mapping real-world objects using define_supertag and instantiate them powerfully utilizing add_tagged_node and add_node_with_fields.
  • Hierarchy & Linking — Push whole outline structures programmatically executing add_node_with_children and enforce complex bi-directional network paths executing add_node_reference.
  • Specialized Datatypes — Effortlessly instantiate formatted daily operations leveraging add_checkbox_task, temporal entries mapping add_date_node, or external resources resolving via add_url_bookmark.

The Tana MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Tana to CrewAI via MCP

Follow these steps to integrate the Tana MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Tana

Why Use CrewAI with the Tana MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Tana through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Tana + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Tana MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Tana for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Tana, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Tana tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Tana against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Tana MCP Tools for CrewAI (10)

These 10 tools become available when you connect Tana to CrewAI via MCP:

01

add_checkbox_task

Optionally set initial done status. Creates a checkbox/todo item in the Tana inbox

02

add_date_node

Format: YYYY-MM-DD. Creates a date-typed node in the Tana inbox

03

add_node

Provide a target node ID (or "INBOX", "LIBRARY") and the node name. Creates a new node in a specific Tana location

04

add_node_reference

Provide a label and the target node ID. Creates a reference node linking to an existing node

05

add_node_with_children

Provide a name and comma-separated children. Creates a parent node with multiple child nodes

06

add_node_with_fields

Provide name, supertag ID, and field data as a JSON object. Creates a supertagged node with structured field values

07

add_tagged_node

g. #meeting, #person). Requires the supertag ID from Tana schema. Creates a new node with a supertag applied

08

add_to_inbox

Quickly adds a new node directly to the Tana Inbox

09

add_url_bookmark

Creates a URL-typed node in Tana

10

define_supertag

Provide a name and description. Defines a new supertag in the Tana schema

Example Prompts for Tana in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Tana immediately.

01

"Add a new conceptual outline to my Inbox. The main title should be 'Quarterly Product Strategy', and it should contain three specific child nodes functioning as checkable tasks."

02

"Create a new node 'Meeting Notes format' structured in our weekly workspace."

03

"Search my Tana knowledge base for nodes tagged with '#project'."

Troubleshooting Tana MCP Server with CrewAI

Common issues when connecting Tana to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Tana + CrewAI FAQ

Common questions about integrating Tana MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Connect Tana to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.