Custom MCP client and saved.md

Give your custom MCP client a publishing workflow.

saved.md exposes MCP tools for publishing pages, reading page source, updating versions, and managing account-backed saved.md links.

Connect Custom MCP

What it does

A custom MCP client can connect AI systems to external tools over a standard protocol. That makes it possible to build your own agent workflow while still using shared publishing infrastructure.

How saved.md fits

With saved.md configured as an HTTP MCP server, your client can publish Markdown, HTML, and JSX pages through OAuth or token-based fallback flows. It is a practical way to add page publishing to an internal AI product or automation.

Workflows

What you can publish from Custom MCP

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

Add page publishing

Let an internal assistant create saved.md links instead of returning only text.

Read and update pages

Use saved.md tools to fetch page source, create new versions, and keep public URLs stable.

Support template workflows

Build flows where the client reads a saved.md template source, adapts it, and publishes a polished page.

Setup

How to connect Custom MCP to saved.md

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

Check client support

Use this path when the client supports remote MCP over Streamable HTTP and can complete OAuth with PKCE or dynamic client registration. If it only accepts a static bearer token, skip to the fallback step.

Add savedmd as an HTTP server

Configure the client with the saved.md MCP URL and no static Authorization header. OAuth-capable clients should discover saved.md auth automatically from the endpoint.

OAuth MCP config

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

Complete OAuth

On first connect or first tool call, the client should open saved.md sign-in in the browser. Sign in, click Allow, and let the client store the returned access and refresh tokens.

Verify tools

Confirm the client can see saved.md tools, especially publish_page, get_page, list_pages, and update_page.

Token-only fallback

If the client does not implement MCP OAuth, create a saved.md MCP token and configure a static Authorization header instead.

Fallback header

Authorization: Bearer smd_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 validation report titled "Custom MCP client publish check".

Write it for the person integrating this MCP client. Include:
- what capability this test proves
- the transport/auth assumption used by the client
- three follow-up checks before relying on it in production
- a final "Connection result" line that confirms the client can publish through saved.md

Keep it under 300 words. Avoid lorem ipsum, placeholders, and vague success language. Return only the saved.md URL plus one sentence summarizing what you published.