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

Gemini CLI and saved.md

Publish Gemini CLI output as shareable pages.

saved.md gives Gemini CLI a publishing target for notes, reports, checklists, and simple websites created from terminal conversations.

What it does

Gemini CLI brings AI assistance into the terminal, where developers can ask for summaries, generate notes, inspect workflows, and produce artifacts close to the work.

How saved.md fits

With saved.md MCP, Gemini CLI can turn command-line context into a public page. It is a practical path for publishing Markdown notes, quick web pages, implementation summaries, and handoff documents without leaving the terminal.

Workflows

What you can publish from Gemini

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

Publish terminal notes

Turn a Gemini CLI answer into a saved.md link that teammates can read outside the terminal.

Create implementation handoffs

Summarize what changed, what to verify, and what to do next as a Markdown page.

Share simple AI pages

Use saved.md when Gemini CLI creates a report, checklist, or lightweight website worth sharing.

Setup

How to connect Gemini to saved.md

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

01

Add MCP server

Run this in the terminal where Gemini CLI is installed. Gemini will discover saved.md OAuth from the MCP endpoint.

Terminal command

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

Sign in with OAuth

Open Gemini CLI and ask it to authenticate the savedmd server. Gemini stores and refreshes its OAuth tokens locally.

Gemini CLI command

/mcp auth savedmd
03

Verify

Confirm savedmd appears in Gemini CLI.

Verify

gemini 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 concise markdown field note titled "Gemini CLI MCP validation".

Write it for a developer who just connected Gemini CLI to saved.md. Include:
- the goal of the connection
- the exact kind of page this test published
- three next prompts they could try after this smoke test
- a final "Connection result" line that says Gemini CLI can publish through saved.md

Keep it under 300 words. Avoid generic filler, empty enthusiasm, and placeholder text. Return only the saved.md URL plus one sentence summarizing what was published.