Quick answer
Vist and Hjarni both connect external assistants through hosted MCP. Vist supports note links and assistant-maintained wiki pages, so those are not exclusive Hjarni features. Compare Vist’s personal notes-and-tasks workflow with Hjarni’s shared team spaces, folder instructions and agent-token permissions.
Details behind the comparison
- Official MCP
- Both document external assistants searching, reading and writing notes.
- Note links
- Vist documents linking notes with [[ and building linked wiki pages from sources.
- Search
- Vist says semantic search uses Mistral embeddings and can be disabled.
- Tasks
- Compare the task workflow you actually need.
- Free MCP plan
- Plan limits checked against current product information.
- Hosting
- Both are hosted services.
- Team and folder permissions
- Do not infer that an unlisted feature is unavailable; confirm with Vist.
- Export
- Test a small transfer before relying on links, metadata or attachments surviving it.
Compare the surrounding workflow
Vist documents a keyboard-first editor, tasks, note links, wiki pages and both MCP and CLI access. Its current free plan includes more notes than Hjarni’s free personal plan. Hjarni’s case rests on its own shared team spaces, folder roles, inherited instructions and separately scoped agent tokens.
Check access and portability
Hjarni OAuth uses account access by default. At sign-in or in Settings > Connections, you can limit each assistant to selected folders, read-only access, or both. Manual agent tokens offer the same folder and read/write controls for compatible clients. Follow the folder-access walkthrough to check the boundary. Instructions guide an assistant but do not enforce permissions or guarantee retrieval. Try a small Markdown export and import before moving a library.