How I Use the DEVONthink MCP Server
For years I treated DEVONthink as the archive I always contemplated using — the place I knew I should be putting everything, but never quite operationalized. The MCP server changed that overnight. DEVONthink is now the single most important tool in my workflow, more central even than my project manager. It went from passive archive to active partner, and everything I produce now flows through it.
A few ways I use it day-to-day:
-
As the primary destination for AI-generated content. When I draft blog posts, campaign briefs, white papers, or research documents in Claude, the final HTML record gets pushed directly into DEVONthink. The MCP server creates properly formatted HTML records, places them in the right group, and applies tags without me ever leaving the chat. Published content and source drafts live side-by-side in the same trusted store.
-
HTML rendering that nothing else in this category matches. This is a big one. DEVONthink renders HTML records natively through WebKit, which means my AI-generated dashboards, briefings, and styled documents display exactly as they will in a browser — fonts, CSS, collapsible panels, embedded styling, all of it. Every other knowledge tool I have tried either strips HTML, flattens it to plain text, or shows raw markup. DEVONthink treats HTML as a first-class document type. That single capability is why I can use AI to produce visually rich, branded internal documents and have them live as native records in my knowledge base rather than as orphaned files.
-
Instant deep links with one-click navigation. Every time Claude creates a record in DEVONthink through the MCP server, it returns the new record’s UUID. Claude immediately renders that UUID as an x-DEVONthink-item:// deep link inside the chat response, paired with a Copy button. One click and I am inside the record in DEVONthink, ready to read, edit, or move it. No searching, no hunting through groups, no copying UUIDs by hand. The deep link is generated and surfaced in the same response that creates the content. This single pattern is what makes the workflow feel seamless — content creation and retrieval collapse into a single step, and nothing I make is ever more than one click away.
-
For daily dashboards and recurring records. I run a daily HTML dashboard that aggregates tasks, calendar events, metrics, and reading notes. The MCP server creates that record each morning in a dedicated Dashboards group, and I update it throughout the day. Over time this builds a searchable journal of every working day, fully styled and instantly readable.
-
For campaign asset organization. Each marketing campaign has its own group in DEVONthink. The MCP server lists everything in a campaign group, creates new assets inside it, and moves records between groups as campaigns evolve. When a teammate asks what we have on a given campaign, I pull a complete inventory in seconds.
-
For prompt and workflow storage. I keep my reusable Claude prompts as records inside DEVONthink, organized by purpose. The MCP server reads those prompts back into a session when I need them, which means my “AI operating system” lives in DEVONthink rather than scattered across apps.
-
For retrieval inside long-running projects. Search, lookup by UUID, and group listing through the MCP server means I can pull historical context into a current conversation without copy-paste. If I wrote about a topic six months ago, I surface that record instantly and build on it.
-
For two-way provenance. Beyond the immediate copy-button workflow, every record carries a stable UUID for the long term. I can reference records across sessions, link between them, and trust that the path back into DEVONthink is permanent.
What I’d want from a first-party server
The community server has been excellent, but a Devon-built MCP would unlock a few things worth highlighting: reliable HTML record updates that preserve UUIDs, native handling of DEVONthink’s AI features (classify, see also, summarize) exposed as MCP tools, group-level operations like bulk tagging and moving, and tighter integration with smart groups and replicants. The bigger opportunity is positioning DEVONthink as the canonical knowledge layer for AI agents — the place where context lives between sessions, rendered the way it was meant to be rendered.