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 app and saved.md

Turn Codex app work into live saved.md pages.

saved.md gives Codex app a way to publish the artifacts it creates while working with a codebase: plans, reports, release notes, dashboards, and template-derived pages.

Connect Codex app

What it does

Codex app works inside a project workspace, reads code, makes changes, and can coordinate technical work with the surrounding context still visible.

How saved.md fits

With saved.md connected, Codex app can publish project knowledge as a web page. That means a release plan, migration brief, QA checklist, or stakeholder readout can leave the thread as a polished link.

Workflows

What you can publish from Codex app

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

Publish project readouts

Ask Codex app to convert implementation context into a stakeholder-ready saved.md page.

Create template-derived pages

Use saved.md templates for polished reports, presentations, roadmaps, and dashboards.

Document codebase decisions

Turn architecture notes, review findings, or release summaries into durable links.

Setup

How to connect Codex app to saved.md

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

01

Configure saved.md MCP

Add saved.md as a remote HTTP MCP server, then complete OAuth when your app asks for authorization.

Codex prompt

Connect saved.md MCP for me using https://mcp.saved.md/api/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.

Publish a polished presentation-style page based on this template:
https://www.saved.md/TQKSh3UOwRGdIhcAcPdAoQoaWMzbK5zX

Cover these sections:
- what saved.md is: an agent-published home for Markdown, HTML, and JSX pages
- how MCP publishing works from Codex app
- template selection and template-derived publishing
- account ownership, version updates, and shareable URLs
- one concrete real-codebase example, such as turning a release plan into a stakeholder-ready page
- a final "Connection result" line that confirms the publish succeeded