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

Codex CLI and saved.md

Publish Codex CLI sessions as pages.

saved.md turns Codex CLI work into shareable links for technical notes, codebase handoffs, release summaries, and Markdown pages.

Connect Codex CLI

What it does

Codex CLI brings agentic coding workflows into the terminal. It can inspect a repository, explain changes, propose implementation plans, and help produce durable project context.

How saved.md fits

With saved.md connected, Codex CLI can publish that context instead of leaving it in terminal scrollback. It is a clean route for Markdown publishing, engineering notes, and simple websites generated from repo work.

Workflows

What you can publish from Codex CLI

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

Publish engineering handoffs

Create a saved.md page that captures what changed, why it changed, and what should be checked next.

Share terminal research

Turn investigation output into a readable page for people who will not read the CLI session.

Create Markdown pages

Ask Codex CLI to publish Markdown, HTML, or JSX when the content should become a public link.

Setup

How to connect Codex CLI to saved.md

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

01

Add MCP server

Add saved.md as a remote Streamable HTTP MCP server.

Codex CLI command

codex mcp add savedmd --url https://mcp.saved.md/api/mcp
02

Sign in with OAuth

Start Codex CLI's OAuth login for the savedmd server and approve access in the browser.

Codex CLI command

codex mcp login savedmd
03

Verify

Confirm savedmd appears in Codex CLI.

Verify

codex mcp list

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 practical markdown handoff titled "Codex CLI MCP publish check".

Make it a useful engineering note, not a toy page. Include:
- what changed when saved.md was connected
- a compact checklist for verifying future CLI-based MCP publishes
- one example of a page Codex CLI could publish from a real codebase
- a final "Connection result" line that confirms the publish succeeded

Keep it under 300 words and avoid lorem ipsum, vague claims, and decorative filler. Return only the saved.md URL plus one sentence summarizing the page.