Docs MD — Markdown Share

What Docs MD — Markdown Share MCP server does

Docs MD — Markdown Share provides a way for an AI assistant to publish Markdown as a public web document. The service renders the content into a reading page and returns a page URL, a raw Markdown URL, the selected expiration, and a private edit token. No account or API key is needed for the documented MCP endpoint.

The service accepts expiration periods of 1 day, 7 days, 30 days, or never. Permanent shares can be indexed by search engines, while expiring shares are served with a noindex directive. Anyone who has a share URL can read it. Expiration removes the page at that URL, but it cannot retract copies that someone already downloaded.

How it works

An AI client connects to https://docs-md.com/api/mcp over streamable HTTP. After a Markdown document is provided, the share_markdown tool creates a share. The response includes the rendered URL and edit token; the token should be treated as private rather than placed in the document or shared reading link.

To revise the same page, the client calls update_share with the share identifier and edit token. delete_share removes it using the same authorization mechanism. This makes Docs MD — Markdown Share MCP server suitable for workflows where an agent publishes an initial draft and later replaces it without changing the link.

The rendered pages can display Mermaid code blocks, syntax-highlighted code, and an automatically generated sidebar table of contents for longer documents. A raw endpoint is also available for retrieving the Markdown source.

Setup and configuration

The remote MCP service requires no API key. Add the endpoint to an MCP-capable editor or assistant, then restart the client if its configuration requires a reload. A Cursor configuration, for example, uses the following server URL:

{
  "mcpServers": {
    "md-share": {
      "url": "https://docs-md.com/api/mcp"
    }
  }
}

The README provides editor guidance for Cursor, Claude Code, VS Code, Windsurf, and Zed. The repository also documents local development commands based on npm, including installation, development mode, type checking, linting, and production builds.

For a self-managed production deployment, documented controls include request-size limits, Markdown character limits, per-IP rate limits, secrets for cleanup and administrative endpoints, and an optional origin allowlist for MCP preflight requests. These settings are environment variables rather than client-side MCP options.

Tools and capabilities

Docs MD — Markdown Share exposes three MCP tools:

• share_markdown creates a public rendered share with optional filename and expiry.
• update_share replaces content on an existing share when the edit token is supplied.
• delete_share removes an existing share when the edit token is supplied.

The underlying REST API offers equivalent create, update, and delete operations, plus GET /raw/:id for the unrendered Markdown. The web interface provides an editor with live preview, but the MCP integration is intended for assistant-driven publishing.

Limitations and notes

Shares are public to anyone with the URL, so the service is not appropriate for confidential documents. Edit tokens grant modification or deletion access and should be stored separately from the published content. Request validation, payload limits, and rate limiting are documented security defaults, but they do not change the public visibility of a share.

The MCP service is remote and streamable HTTP rather than a local stdio process. Expiry values are limited to the documented choices, and a permanent share is represented by an expiresAt value of zero in the API response. The project is licensed under MIT.