MDflow

Agent-controllable markdown workspace. Folders hold .md documents an AI agent can read, create, update, organize, and share. Control it via the MCP server (preferred) at https://mdflow.cz/api/mcp or the REST API at https://mdflow.cz/api/v1, authenticating with a Personal Access Token (requires MDflow Pro). Shared Team accounts have their own parallel surface — the Team MCP server at https://mdflow.cz/api/team/mcp and the Team REST API at https://mdflow.cz/api/team/v1, authenticated with a Team access token (mdt_…). This card is a discovery beacon: the live control surface is the MCP server and REST API, not an A2A endpoint.

Skills

• Manage markdown documents
  List, read, create, rename, move, and delete markdown documents in folders you own. Each document carries its full path (workspace → … → document) and a compounded description — the workspace+folder context cascade.
  markdowndocumentscrud
• Manage workspaces
  List, create, rename, describe, and delete workspaces, the top-level bucket above folders that every folder belongs to.
  workspacesorganize
• Organize folders
  List, read (with full path and the compounded description cascade from workspace down to folder), create, rename, move, and delete folders, and edit folder descriptions, which act as retrieval context for the documents inside.
  foldersorganize
• Topic-based retrieval
  Find the most relevant markdown by ranking folder descriptions first, then titles, then fetching the best-matching document bodies. When a topic clearly belongs to one workspace, pick the best-matching workspace first and pass workspaceId to scope retrieval there; omit it for broad or ambiguous topics to rank across the whole account.
  searchretrievalrag
• Share documents
  Turn on public unguessable share links (optionally with comments), or privately share a document with specific people by email.
  sharingpublish
• Work in a Team account
  Read and write the shared workspaces, folders, and markdown documents of an MDflow Team account, using a Team access token (mdt_…) against the Team MCP server at https://mdflow.cz/api/team/mcp (16 mdflow_team_* tools) or the Team REST API at https://mdflow.cz/api/team/v1. A token is bound to one Team account, granted only the workspaces chosen when it was created, and capped at read-only or read-and-write; every request re-checks the creator's live membership, role, and per-workspace permission. Content only — membership, invitations, and billing are not exposed. Personal tokens are rejected on Team routes and Team tokens on personal routes.
  teamcollaborationworkspacesdocuments

How to call

https://mdflow.cz/api/mcp

Listed in

Directories this entry was found in.