Can my agent add specific content like code blocks or callouts to a Page?

Yes. Use the 'append_block' tool. You can specify the 'type' (text, heading, list, code, callout, or checklist) and provide the Markdown content. The agent will translate this directly to native Craft Block UUID endpoints.

How do I retrieve my task list across all my Craft documents?

Use the 'list_tasks' tool. Your agent will sweep through your workspace configurations and request absolute arrays isolating all Task nodes, allowing you to see all pending items in one view.

Can I access my Daily Notes journal through the agent?

Absolutely. The 'get_daily_note' tool retrieves temporal records by date. Your agent can fetch the exact Page linked to a specific day in your Calendar, letting you read or update your journals seamlessly.

Craft (Docs & Notes) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Craft (Docs & Notes)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Craft (Docs & Notes) Specialist",
    goal="Help users interact with Craft (Docs & Notes) effectively",
    backstory=(
        "You are an expert at leveraging Craft (Docs & Notes) 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 Craft (Docs & Notes) "
        "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)

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 Craft (Docs & Notes) MCP Server

Connect your Craft.do account to any AI agent and take full control of your premium writing experience and collaborative workspace through natural conversation.

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

What you can do

Document Navigation — List and search all documents within your folders to identify specific workspace boundaries and content classifications
Block-Level Operations — Retrieve detailed Block trees and append new structural elements (headings, lists, code, checklists) to any existing Page
Agile Document Creation — Provision new highly-available Documents with specific Markdown content and titles natively from your chat
Daily Note Management — Fetch temporal records and intricate networking mappings from your Calendar to audit daily journals and tasks
Task & Checklist Tracking — Extract comprehensive mapped checklists across your workspace to monitor active progress and pending items
Content Mutation — Safely substitute explicit Document values by patching Block trees and overwriting content limits through the REST API

The Craft (Docs & Notes) 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 Craft (Docs & Notes) to CrewAI via MCP

Follow these steps to integrate the Craft (Docs & Notes) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Craft (Docs & Notes)

Why Use CrewAI with the Craft (Docs & Notes) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Craft (Docs & Notes) through the Model Context Protocol.

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

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

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

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

Craft (Docs & Notes) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Craft (Docs & Notes) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Craft (Docs & Notes) for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Craft (Docs & Notes), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Craft (Docs & Notes) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Craft (Docs & Notes) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Craft (Docs & Notes) MCP Tools for CrewAI (10)

These 10 tools become available when you connect Craft (Docs & Notes) to CrewAI via MCP:

append_block

Perform structural injection of properties driving new Blocks

create_document

Provision a highly-available JSON Payload generating new Document rows

delete_document

Irreversibly vaporize explicit App nodes dropping live Document rows

get_daily_note

Retrieve elaborate explicit mapping properties limiting Daily Pages

get_document

Retrieve explicit UX logging tracing explicit Document IDs limitlessly

list_blocks

Enumerate explicitly attached structured rules exporting active Blocks

list_documents

Identify bounded routing spaces inside the Craft workspace

list_tasks

Gather comprehensive mapped checklists limiting cross-workspace Tasks

search_documents

Execute static listing mapping structural Text queries via Search

update_document

Mutate global Web Context boundaries substituting explicit Document values

Example Prompts for Craft (Docs & Notes) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Craft (Docs & Notes) immediately.

"List all my documents in Craft"

"Add a checklist item to document 'doc_123': 'Review API security'"

"What's in my daily note for today?"

Troubleshooting Craft (Docs & Notes) MCP Server with CrewAI

Common issues when connecting Craft (Docs & Notes) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

Rate limiting or 429 errors

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

Craft (Docs & Notes) + CrewAI FAQ

Common questions about integrating Craft (Docs & Notes) MCP Server with CrewAI.

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.

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.

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.

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.

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.