Markdown by mdedit.ai

View saved version →

---
name: find-mdedit-document
description: Find and read an existing Markdown Document stored in mdedit. Use when the user asks to locate, open, retrieve, quote, summarize, or inspect a saved mdedit document. Do not use for local files, web pages, or generic Markdown questions unrelated to mdedit storage.
compatibility: Requires the mdedit MCP server with workspace and article read tools.
---

# Find and read a document in mdedit

Resolve a real saved document before describing its content.

1. Resolve the workspace with `list_workspaces` unless a `workspaceId` from an earlier mdedit tool result is already established.
   - If several workspaces could match, ask the user to choose by returned name.
   - If no workspace matches, stop without guessing.
2. Call `list_articles` for the resolved workspace.
3. Match the user's title or description against returned document metadata.
   - If there is one clear match, continue.
   - If several documents plausibly match, present only their returned titles and ask the user to choose.
   - If there is no match, say so and stop.
4. Call `read_article` with the returned `workspaceId` and `articleId`.
5. Answer from the returned saved `content`, `contentRevision`, and `contentHash`. Distinguish exact saved content from any summary or interpretation.

This workflow is read-only. Do not call create, edit, publish, or unpublish tools. Never infer document content, identifiers, revisions, publication status, or URLs from titles or conversation memory.

Referenced files: 1

View saved version →

---
name: publish-mdedit-document
description: Check or change Public Document Publishing for an existing mdedit Markdown Document. Use when the user explicitly asks to publish, unpublish, inspect publication status, or create or update a public mded.it link. Do not use for private editor links, local files, or generic sharing advice.
compatibility: Requires the mdedit MCP server with publishing tools and explicit confirmation fields.
---

# Manage Public Document Publishing

Public visibility is a separate, explicit action. Never treat saving or editing as permission to publish.

1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned match is ambiguous.
2. Call `get_publish_status` before proposing a mutation.
3. For a status-only request, report only the returned state and exact returned URL fields, then stop without mutating.
4. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request.
5. After confirmation, call `publish_article` with `confirmPublic: true`. Include a custom slug or SEO metadata only when the user supplied or approved it.
6. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing.
7. Before disabling a public link, identify the current returned link and ask for explicit confirmation. After confirmation, call `unpublish_article` with `confirmUnpublish: true`.

Never construct an `mded.it` URL, expose an editor URL as a public link, or claim publication from a requested slug. On denied permission, failure, or missing result fields, report the bounded error and leave visibility unchanged.

Referenced files: 1

View saved version →

---
name: revise-mdedit-document
description: Safely revise an existing Markdown Document stored in mdedit with anchored, conflict-aware edits. Use when the user asks to update, rewrite, correct, insert, remove, or reorganize content in a saved mdedit document. Do not use for unsaved local Markdown, local files, or generic editing advice.
compatibility: Requires the mdedit MCP server with read_article and edit_article tools.
---

# Revise a document in mdedit

Read the current durable content, then apply the smallest unambiguous anchored change.

1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned workspace or document match is ambiguous.
2. Confirm the requested change is specific enough to apply. Ask a focused question when the target text, section, or replacement is unclear.
3. Build one or more `edit_article` operations:
   - Prefer a unique `quote` anchor with nearby `context`.
   - Use `afterHeading`, `beforeHeading`, or `inSection` for section changes.
   - Use a numeric range only when it came from current tool-returned content.
   - Avoid whole-document replacement unless the user requests a full rewrite.
4. Pass the current `contentHash` from `read_article` as `ifContentHash`.
5. Treat the edit as successful only when the result has no conflicts and returns new durable `content`, `contentRevision`, and `contentHash`.
6. Summarize what changed and report the returned revision.

If the tool reports a hash mismatch or any conflict, stop, read the document again, and explain what changed concurrently. Do not retry against a new version without reconciling the user's intent. Never overwrite ambiguity, invent anchors, or claim success from requested text alone.

Referenced files: 1

View saved version →

---
name: save-mdedit-document
description: Create and durably save a private Markdown Document in mdedit. Use when the user explicitly asks to save, persist, archive, or turn conversation content into a document in mdedit. Do not use for generic Markdown writing, formatting, or local-file creation that does not require mdedit storage.
compatibility: Requires the mdedit MCP server with list_workspaces and create_article tools.
---

# Save a document to mdedit

Create one durable private document from content the user supplied or asked you to draft.

1. Determine the intended title and Markdown content. Ask a focused question if the source material or document boundary is unclear.
2. Resolve the destination workspace:
   - Use an established `workspaceId` only when it came from an earlier mdedit tool result.
   - Otherwise call `list_workspaces`.
   - If exactly one workspace is returned, use it. If several are returned, ask the user which returned workspace name to use. If none are returned, stop.
3. Call `create_article` once with the returned `workspaceId`, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration.
4. Treat the save as successful only when the tool returns `workspaceId`, `articleId`, `contentRevision`, `contentHash`, and `editorUrl`.
5. Report the saved title and exact returned `editorUrl`. State that the document remains private.

Never invent or reconstruct a workspace ID, document ID, revision, hash, or editor URL. Never call a publishing tool as part of this workflow. If creation fails or reports retained partial state, report that bounded failure and do not claim the document was saved.

Referenced files: 1