MCP (Model Context Protocol) is an open standard that lets AI tools call external services. MDtoLink's MCP server lets Cursor's AI publish and update markdown documents on your behalf. Read the full explainer on our blog.

Can Cursor's AI update an already-published doc?

Yes. The MCP server supports both publishing new documents and updating existing ones. The AI can re-publish the same file and the URL stays the same.

Do I need both CLI and MCP?

No. Pick one. Use the CLI for manual control from the terminal. Use the MCP server if you want Cursor's AI to handle publishing for you. Both produce the same result.

Does the MCP server need my API key?

Yes. The MCP server uses your MDtoLink authentication. Run 'mdtolink login' first to authenticate, then the MCP server picks up your credentials automatically.

Integration Guide

Publish markdown from Cursor

Two ways to publish from Cursor: use the CLI from the built-in terminal, or connect the MCP server and let Cursor's AI publish for you. Pick the approach that fits how you work.

Option 1: CLI from the terminal

Cursor has a built-in terminal, same as VS Code. Open it and run the CLI directly.

1. Install the MDtoLink CLI

npm install -g mdtolink

2. Open the terminal in Cursor

Press Ctrl+` on Linux/Windows or Cmd+` on macOS.

3. Publish the file

mdtolink publish README.md

Option 2: MCP server (AI-driven)

Connect MDtoLink's MCP server to Cursor and the AI can publish documents for you. Ask it to "publish this file to MDtoLink" and it handles the rest.

1. Authenticate first

Run this once to log in:

npx mdtolink-mcp@latest

2. Add the MCP config to Cursor

Open Cursor's MCP settings and add the MDtoLink server:

{
  "mcpServers": {
    "mdtolink": {
      "command": "npx",
      "args": ["mdtolink-mcp@latest"]
    }
  }
}

3. Ask the AI to publish

In Cursor's AI chat, ask it to publish your file:

"Publish docs/api-reference.md to MDtoLink"

The AI calls the MCP server, publishes the file, and returns the URL in the chat.

Why this workflow

Cursor is built for AI-assisted coding. MDtoLink's MCP server plugs into that loop: the AI writes the docs, the AI publishes the docs. You review the URL.

✓ AI generates, AI publishes. Ask Cursor to write a doc and publish it in one prompt. No manual steps between generation and sharing.
✓ CLI fallback. When you want manual control, the terminal is right there. Same CLI, same commands as any other editor.
✓ No context switch. Whether you use MCP or CLI, you stay in Cursor. No browser tabs, no upload forms.
✓ Great for AI agent reports. Build agents that generate analysis, status reports, or summaries, then publish them automatically.

Frequently asked questions

What is MCP?: MCP (Model Context Protocol) is an open standard that lets AI tools call external services. MDtoLink's MCP server lets Cursor's AI publish and update markdown documents on your behalf. Read the full explainer on our blog.
Can Cursor's AI update an already-published doc?: Yes. The MCP server supports both publishing new documents and updating existing ones. The AI can re-publish the same file and the URL stays the same.
Do I need both CLI and MCP?: No. Pick one. Use the CLI for manual control from the terminal. Use the MCP server if you want Cursor's AI to handle publishing for you. Both produce the same result.
Does the MCP server need my API key?: Yes. The MCP server uses your MDtoLink authentication. Run 'mdtolink login' first to authenticate, then the MCP server picks up your credentials automatically.

Learn more about what MCP is, or read the MCP setup guide. See AI agent reports for more on automated publishing.

Publish from Cursor in under five minutes

Pick CLI or MCP, set it up once, and start publishing. Both approaches work with the free plan.

Get started free Read the docs

Free plan includes 5 documents. View pricing for higher limits.