saved.md

For agents

You are on saved.md.

This site hosts public pages created by signed-in users from Markdown, HTML, or JSX. If the user asks you to publish or update one, use their saved.md MCP connection.

  • Publish: use the user's saved.md MCP connection when available. If saved.md tools are missing, help the user connect or reauthorize saved.md in their current AI app, then verify tools like publish_page and get_page are visible.
  • Update/copy: call get_page, then call update_page with the returned currentVersion as expectedCurrentVersion when the signed-in user owns the page or has collaborator edit access. Otherwise fetch source, edit it, then create a new page for the signed-in user.
  • If the app says saved.md is connected but tools still are not visible in this chat, ask the user to start a new chat or reload the app so the MCP tool list refreshes.

Agent guide: /install.md

MCP setup: /mcp.md

All tools

Cursor and saved.md

Publish Cursor Agent work as saved.md pages.

saved.md lets Cursor turn codebase context into web pages, Markdown handoffs, reports, and small websites that are easy to share.

Connect Cursor

What it does

Cursor combines an AI coding environment with repository context, making it useful for generating summaries, implementation notes, architecture explanations, and project plans.

How saved.md fits

With saved.md MCP, Cursor can publish those outputs as real links. Instead of sending a screenshot or copying editor text, you can ask Cursor to create a saved.md page from the current repo context.

Workflows

What you can publish from Cursor

These are the patterns where saved.md turns AI output into something easier to share than a chat transcript.

Publish architecture notes

Ask Cursor to explain a subsystem and publish the result as a saved.md page.

Share implementation plans

Turn planning or review output into a simple website for teammates.

Create repo-aware pages

Use saved.md when Cursor drafts a report, checklist, or Markdown page from project files.

Setup

How to connect Cursor to saved.md

Connect Cursor to saved.md with the MCP URL https://mcp.saved.md/api/mcp. Once authorization is complete, ask Cursor to publish or update a saved.md page.

01

Choose where to configure it

Use ~/.cursor/mcp.json if you want saved.md in every Cursor workspace. Use .cursor/mcp.json inside a repo if this connection should stay project-specific.

Config paths

~/.cursor/mcp.json
.cursor/mcp.json
02

Add the savedmd server

Create the file if it does not exist, or merge this savedmd entry into the existing mcpServers object. The HTTP URL lets Cursor discover saved.md OAuth automatically.

mcp.json

{
  "mcpServers": {
    "savedmd": {
      "type": "http",
      "url": "https://mcp.saved.md/api/mcp"
    }
  }
}
03

Reload Cursor

Reload Cursor or reopen MCP settings so it picks up the new mcp.json entry. savedmd should appear as an HTTP MCP server.

04

Sign in with OAuth

When Cursor asks to authenticate savedmd, complete the browser sign-in and approve saved.md access. If the prompt does not appear, start OAuth from Cursor CLI.

Cursor CLI command

cursor-agent mcp login savedmd
05

Verify

Confirm savedmd is connected, and optionally inspect the tools Cursor can see.

Verify

cursor-agent mcp list
cursor-agent mcp list-tools savedmd

Try it

A practical test prompt

After connecting saved.md, use a prompt like this to verify the tool can publish a real page.

Use saved.md to publish a concise markdown architecture note titled "Cursor MCP connection check".

Make it useful for someone joining the project. Include:
- the role saved.md plays in the workflow
- three concrete page ideas Cursor could publish from a repo
- one guardrail for keeping generated pages high quality
- a final "Connection result" line that confirms Cursor can publish through saved.md

Keep it under 300 words. Avoid placeholder text, vague architecture language, and filler. Return only the saved.md URL plus one sentence summarizing the page.