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

Claude Code and saved.md

Turn Claude Code sessions into published pages.

saved.md gives Claude Code a way to publish useful project output: Markdown notes, reports, release pages, and simple web pages.

What it does

Claude Code works in developer environments where it can inspect code, reason about changes, and help carry implementation work forward.

How saved.md fits

With saved.md connected, Claude Code can publish the useful parts of that work as durable pages. It is especially helpful for codebase summaries, release notes, migration plans, and verification checklists.

Workflows

What you can publish from Claude Code

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

Publish release notes

Turn the result of a coding session into a clean page for product or engineering readers.

Create developer handoffs

Share what changed, open questions, and follow-up checks as a saved.md link.

Document repo context

Publish architecture notes or project summaries without creating another doc file.

Setup

How to connect Claude Code to saved.md

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

01

Add MCP server

Run this where Claude Code is installed. Claude Code will discover saved.md OAuth from the MCP endpoint.

Claude Code command

claude mcp add --transport http savedmd https://mcp.saved.md/api/mcp
02

Sign in with OAuth

Open Claude Code, run /mcp, choose savedmd, and follow the browser login flow.

Claude Code command

/mcp
03

Verify

Confirm savedmd appears in Claude Code.

Verify

claude mcp list
/mcp

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 markdown release note titled "Claude Code MCP publish check".

Write it as if this repository just gained a working saved.md MCP connection. Include:
- a concise summary
- three practical developer workflows now enabled
- one verification step for future releases
- a final "Connection result" line that confirms Claude Code can publish through saved.md

Keep it under 300 words. Avoid generic release-note filler, fake version numbers, and placeholders. Return only the saved.md URL plus one sentence summarizing the note.