$cat connect/cursor.md

MDflow for Cursor.

Open VSX · Pro

Cursor is an AI-first editor, and MDflow is the durable markdown memory your AI works from. Connect MDflow's MCP server and Cursor's agent can read and write your notes, specs, and context as it codes. The MDflow Workspace extension gives you the other half: the same workspace in Cursor's sidebar, so you can read, edit, and curate that memory by hand — in the same window, without a browser tab.

One source of truth, two hands on it — the agent's and yours:

›Your workspaces, folders, and documents as a native tree in the Explorer.
›Edit any document as a real markdown tab and save back with Ctrl/Cmd + S — the same file your agent reads next.
›Create, rename, move, and delete workspaces, folders, and documents from the tree.
›Encrypt private documents locally — kept out of search and opaque to any agent.

Also installs in Windsurf, VSCodium, and other Open VSX editors. The extension is free and open source; editing needs MDflow Pro, the same plan that unlocks the MCP server and API.

$why cursor

The human editor for your AI's memory

An AI editor is only as good as the context it can reach. Keep that context in MDflow and it becomes a knowledge base your agent reads and writes over MCP — while you keep a real editor over the exact same documents.

›Curate what the agent reads. Architecture decisions, coding conventions, product specs, and TODOs live in MDflow; you shape them by hand, and mdflow_get_context feeds the right ones to Cursor on demand.
›Review what the agent writes. When the agent updates a document over MCP, you open it in the sidebar and edit it like any file — automatic version history keeps every prior version on the web.
›No context-switch. The memory lives in the same window as the code it describes — no second app, no browser round-trip.
›Portable, not locked in. It is plain markdown you own, reachable from the web, mobile, the API, and any MCP client — Cursor today, another editor tomorrow.
›Private when it needs to be. Client-side encryption keeps secrets out of both search and the agent surface.

$one workspace, two hands

How the agent and you share one workspace

MDflow sits in the middle. Cursor's AI reaches it over the MCP server; you reach it through this extension. Both act on the very same documents.

Cursor AI — over MCP

reads context via mdflow_get_context

writes back decisions and notes as it works

authenticated with a Personal Access Token

You — MDflow Workspace extension

edit the same docs as markdown tabs

curate folders that shape what the agent retrieves

save writes the file the agent reads next

Illustration — the agent and the human editing one shared MDflow workspace.

Set up the agent side: The extension and the MCP server are independent — connect either or both. Connect Cursor's AI over MCP →

$install

Install from Open VSX

Cursor, Windsurf, and VSCodium install extensions from the Open VSX registry rather than the Visual Studio Marketplace — the extension is published to both.

Search the Extensions view

Open the Extensions view (Ctrl/Cmd + Shift + X), search for MDflow Workspace, and click Install — or open the Open VSX listing and install from there.

Cursor — Extensions (Open VSX)

MDflow Workspace

Browse and edit your MDflow markdown · DataOps

Install

Illustration — the extension on Open VSX.

Open the MDflow view and sign in

A new MDflow view appears in the Explorer. Open it and click Sign in to MDflow, or run MDflow: Sign In from the Command Palette.

$sign in

Connect your MDflow account

Two ways to connect. Credentials are stored in the editor's encrypted Secret Storage — never in a settings file.

Field	What to enter
Sign in with browser	An OAuth sign-in in your browser that returns to the editor automatically — no token to copy.
Personal Access Token	Paste a token (`mdf_…`) from mdflow.cz/settings. This is also the token Cursor's AI uses to reach the MCP server — one token, both halves.

MDflow Pro required: Reading and editing go through MDflow's API, a Pro feature — the same subscription that unlocks the MCP server and Personal Access Tokens. A free account can sign in but every request returns Pro plan required until you upgrade.

$browse + edit + save

Browse, edit, and save

The tree loads lazily: expand a workspace for its folders, and a folder for its documents. Click a document to open its body as a markdown tab backed by a virtual mdflow: file system — syntax highlighting, preview, folding, and dirty-state all work as they do for a local file. Ctrl/Cmd + S writes it back to MDflow (bodies over 500 KiB are rejected with a clear message).

›Full CRUD from the tree — create, rename, move, and delete workspaces, folders, and documents; the tree always shows the server-returned name.
›Encrypt sensitive documents with a per-file password (PBKDF2-600k → AES-256-GCM), byte-compatible with the web app and the mdflow-crypt CLI. There is no password recovery.
›Last write wins — the extension is a live API client, not a sync engine, so there is no offline mode or conflict resolution; the most recent save is the one that sticks.

Want the full feature tour?: The VS Code guide walks through every screen in depth — the mechanics are identical across both editors. Read the VS Code guide →

$man troubleshooting

Troubleshooting

MDflow for Cursor troubleshooting: symptoms and fixes
Symptom	Cause & fix
Extension not found in search	Cursor uses Open VSX, not the Visual Studio Marketplace. Search `MDflow Workspace`, or install from the Open VSX listing.
`Pro plan required` on every action	The MDflow API is a Pro feature. Upgrade to Pro — the same plan that unlocks the MCP server your agent uses.
The agent can't see my edits	The extension and the MCP server are separate connections. Connect the agent side too — see the MCP guide.
Save is blocked	A document body cannot exceed 500 KiB — the limit is enforced before the request is sent.

Install from Open VSX →Connect the agent over MCP →The VS Code guide →

> MDflow for Cursor.