Markdown in, hosted page out

MintPage exposes one endpoint. You POST a JSON-RPC tools/call for publish_page and get back a URL. No SDK, no sessions, no OAuth dance.

curl

curl -X POST https://mintpage-mcp.netlify.app/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_page","arguments":{"title":"Hello","content":"# Hi\nMinted from curl."}}}'

The response contains url, page_id, slug and expires_at. Add Authorization: Bearer mp_… for a keyed account.

Rendering

• GFM Markdown (tables, task lists, fenced code, strikethrough)
• HTML is sanitized server-side: scripts, forms, iframes and external CSS removed; inline styles, <style> blocks and inline SVG kept
• Themes: paper, ink, terminal
• Every page gets an auto-generated preview image for social cards

Why MCP and not REST

Because the callers are agents. MCP gives them tool discovery (tools/list) and typed arguments, so any MCP client can use MintPage without reading docs. The transport is still plain HTTP, which is why curl works.

Limits and pricing

Guest 3/day for 24h, 250 KB each · Free 10 pages for 7 days, 1 MB each · Pro $5/mo or $39/yr: 500 pages, 2 MB each, permanent, custom slugs, indexable, no badge.