Obsidian Publish MCP Server for CrewAI 5 tools — connect in under 2 minutes
Connect your CrewAI agents to Obsidian Publish through Vinkius, pass the Edge URL in the `mcps` parameter and every Obsidian Publish tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Obsidian Publish Specialist",
goal="Help users interact with Obsidian Publish effectively",
backstory=(
"You are an expert at leveraging Obsidian Publish 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 Obsidian Publish "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 5 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 Obsidian Publish MCP Server
Connect your Obsidian Publish environment to your AI agent and construct an intelligent oracle that reads smoothly from your personal or corporate markdown knowledge base.
When paired with CrewAI, Obsidian Publish becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Obsidian Publish 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
- Vault Crawling — Programmatically fetch your entire published vault structure utilizing
list_filesandlist_navigationto build contextual trees. - Direct Note Access — Execute
get_fileto stream the complete raw markdown contents of any note directly into your chat workflow for fast summarization. - Metadata Operations — Use
get_metadatato retrieve frontmatter properties, tags, and internal link logic mapped by Obsidian. - Site Auditing — Easily ping
site_infoto ensure connectivity and verify the deployment status of your target Obsidian publish endpoint.
The Obsidian Publish MCP Server exposes 5 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 Obsidian Publish to CrewAI via MCP
Follow these steps to integrate the Obsidian Publish 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 5 tools from Obsidian Publish
Why Use CrewAI with the Obsidian Publish MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Obsidian Publish 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 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
Obsidian Publish + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Obsidian Publish MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Obsidian Publish 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 Obsidian Publish, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Obsidian Publish 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 Obsidian Publish against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Obsidian Publish MCP Tools for CrewAI (5)
These 5 tools become available when you connect Obsidian Publish to CrewAI via MCP:
get_file
Retrieve exact textual file content and binary assets
get_metadata
Extract internal creation hashes mapping a specific Markdown page
list_files
List all explicitly published raw file paths across the Obsidian workspace
list_navigation
Visualize structurally formatted Markdown navigation trees
site_info
Identify global configuration and styling mapping the site
Example Prompts for Obsidian Publish in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Obsidian Publish immediately.
"Check the vault and list all the files currently publicly available."
"Read the contents of 'System Requirements 2026.md'."
"Fetch the metadata and tags applied to my 'Inbox' note."
Troubleshooting Obsidian Publish MCP Server with CrewAI
Common issues when connecting Obsidian Publish to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Obsidian Publish + CrewAI FAQ
Common questions about integrating Obsidian Publish MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Obsidian Publish with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Obsidian Publish to CrewAI
Get your token, paste the configuration, and start using 5 tools in under 2 minutes. No API key management needed.