Not Currently Supported

An honest list of what MDflow does not do, so you can decide against it quickly rather than discover a gap three weeks in.

Collaboration

• No real-time multi-user collaborative editing. No shared cursors, no simultaneous editing. MDflow is a single-author tool that shares its output.
• No comment replies, threads, approval workflows, resolve states, or assignment. Comments are flat.
• No preview-anchored annotations — comments attach to the markdown source, not the rendered preview.
• No notifications of any kind. Nothing emails you when someone comments.

Organization

• No tags. Folders, collections and search only.
• No manual sort order. Folders and documents are always alphabetical. Number your titles if order matters.
• No nested collections, and no collections of collections.

Deletion

• No trash, no soft delete, no restore. Every deletion is immediate and permanent.

The only exceptions: Google Drive deletions go to Drive's Trash, and version history (Pro) can recover a document's body — but not a deleted document.

Sharing

• No custom public share URLs. Slugs are randomly generated; you cannot choose a readable one.
• No password-protected share links. The model is unlisted links, or private email shares (Pro). Encryption is the closest thing to a password on a share.
• No expiring links. A link works until you turn it off.
• No view analytics. MDflow does not tell you who opened a share, or how often.

Mobile

• No mobile image upload — desktop only.
• The iOS app has no offline access, no images, no PDF export, no share links, no collections, no comments, and no tasks. It also cannot create workspaces, move folders, or remove encryption. See 02 iOS App.

Accounts and access

• No email-and-password sign-in. Google, Apple, GitHub and Microsoft only.
• No teams, organizations, or shared ownership. Documents belong to one account. Private sharing grants read or comment access — never co-ownership.
• No read-only or workspace-scoped Personal Access Tokens. A token grants full read/write access to your entire account. This is the sharpest edge in the product if you are connecting agents.
• No SSO, SCIM, or audit logs beyond token last-used dates.

API and automation

• No API access to version history — deliberate; history is owner-only.
• No API access to collections, comments, search or export.
• No cross-workspace folder moves via API or MCP — web app only.
• No webhooks. The n8n trigger polls; there is no push. MDflow has no "changed since" parameter, so every poll re-fetches the full list.
• No pagination on n8n Get Many operations.

Editor

• No command palette, quick-open, or vim mode.
• No manual theme toggle — it follows your system appearance.
• No WYSIWYG. You write markdown. The preview renders it.

Things that are limits, not gaps

Worth separating, because these are guarantees rather than missing features:

• Encrypted documents are not searchable, not readable by agents, cannot hold uploaded images, and cannot be recovered without the password. That is encryption working. Any of these "fixed" would break the promise.
• Version history is invisible to the API and MCP. That is what makes it a reliable recourse against an agent's mistake.
• drive.file only reaches files you picked. That is least privilege, not an incomplete integration.

What this list is for

If something above is a dealbreaker, MDflow is telling you now.

If none of it is, the trade is this: MDflow does fewer things than a Notion or a Confluence, and in exchange your content stays plain markdown that you can export in one click, read in any editor, and hand to any AI agent without a conversion step.

That is the whole product thesis. The list above is its cost.