Both offer official read and write tools
Joplin's MCP server runs through the desktop Web Clipper. Enable the server, choose the tools, and authenticate with the Web Clipper token. The official Claude Desktop example uses an mcp-remote bridge. Its default listener is local, so that setup does not directly serve remote-only clients.
Hjarni's official MCP endpoint is hosted. Compatible assistants can connect without your desktop staying awake. This simplifies remote access; it does not guarantee tool use or uninterrupted service.
Permissions and privacy are separate choices
Joplin starts with its MCP tools disabled, including the write tools. Once enabled, the AI client controls its own approval flow. Hjarni offers manual folder/space-scoped agent tokens with read/write permissions, while its ordinary OAuth connection is account-wide.
Joplin's end-to-end encryption protects synced data. It does not make a cloud AI conversation local: Joplin explicitly warns that the connected app may send retrieved content to its model provider. Use a local model if keeping processing on the machine is your requirement.
Joplin supports actual collaboration
Joplin Cloud users can share notebooks and edit shared notes, including with encryption enabled. The Teams plan adds sharing permissions. Hjarni offers shared team knowledge with folder roles and instructions.
Joplin's local app is free and open-source, with a choice of sync backends. Cloud storage and email-to-note are paid services. Compare those needs separately from MCP hosting.
Migration is a format change
Joplin supports Markdown exports and its own JEX backup format. Hjarni's Markdown ZIP importer accepts Markdown, not a JEX backup. Check note links, attachments, and notebook structure with a sample first; neither the Joplin database nor its complete history is recreated by importing text files.