MCP Integration & Automation
Keep your knowledge base automatically up to date: external systems maintain content directly via the Model Context Protocol.
The Model Context Protocol (MCP) makes it possible to connect external systems directly to the knowledge base. CRMs, CMSs, project management platforms and document management systems can feed in, update and maintain content automatically — with no manual intervention.
The result: the knowledge base stays current at all times. New documents from day-to-day business flow in automatically. Outdated content is detected and can be targeted for replacement. Editorial effort decreases, quality increases.
MCP integration is suited both to remote maintenance by internal teams and to embedding in existing enterprise workflows — fully API-driven, with no need for direct platform access. The knowledge-base upload also now accepts Markdown files (.md) — the natural exchange format for AI clients.
MCP and open AI models: keeping knowledge automatically up to date →MCP Integration & Automation — step by step
Open MCP Access
Open the Companion under Settings → MCP Access. This view is reserved for organisation owners and admins; members without an admin role see an explanatory notice instead.
Create an access key
Click "New Access Key", give it a name (one key per client) and choose the permissions: Read (search and read entries and tags) or Write (propose changes). The key is displayed only once after creation — copy it immediately and store it securely, it cannot be retrieved again.
Connect an AI client
Point your AI client at the MCP endpoint. For Claude Code the command is: claude mcp add violet-dragonfly --transport http https://violet-dragonfly.fly.dev/mcp --header "Authorization: Bearer vd_mcp_…". The client then has tools for searching, reading entries in full, tag management, and — with write permission — creating and updating entries.
Confirm write operations
Changes via a write client are never saved directly. Every write call creates a pending change with a readable preview and returns a change_id. Only confirm_change(change_id) applies the change; cancel_change discards it. Unconfirmed changes expire after 30 minutes. Every step is recorded with a timestamp and key identifier in the audit trail.
Revoke a key
Click "Revoke" in the key's row and confirm the dialog. The revocation takes effect immediately — the very next request with that key is rejected. The step cannot be undone; the revoked key remains visible in the list, greyed out.
Upload Markdown files
The knowledge-base upload — by click or drag-and-drop — now accepts .md files alongside PDF, DOCX and PPTX. Content is imported verbatim: headings, lists and code blocks are preserved. The file is indexed for search, receives an automatic AI summary, and is fully readable by MCP clients.
The human stays at the centre — AI amplifies, it never replaces.
See it in action
Explore the platform or talk to a companion about your use case.