Documentation

Connect Repage to your AI assistant

The Repage MCP server lets any compatible AI assistant publish and update HTML documents for you. No copy-pasting — just ask your AI to publish, and it returns the shareable link.

Claude CodeCLIOne terminal command. Browser OAuth handles the rest.Claude.aiWebAdd via Settings → Integrations. No API key needed.ChatGPTWebAdd a custom connector in developer mode.CursorIDEAdd a remote server in Cursor Settings → MCP.WindsurfIDEEdit mcp_config.json in your Windsurf settings.

Fastest way: let your agent do it

If you use a coding agent (Claude Code, Cursor, Windsurf, ChatGPT developer mode…), you don't need to follow any steps yourself. Paste the prompt below and your agent will add the Repage server using its own configuration and walk you through sign-in.

Paste this to your AI agent
Add the Repage MCP server to your tools so you can publish HTML documents to shareable links.

It is a remote, streamable-HTTP MCP server at:
https://www.repage.app/api/mcp

Please add it using whatever MCP configuration you support (e.g. `claude mcp add --transport http repage https://www.repage.app/api/mcp`, an mcp.json/mcp_config.json entry with that URL, or your IDE's "add remote MCP server" setting). Name it "repage".

It authenticates with OAuth — when prompted, open the authorization URL so I can sign in with Google. Once connected, confirm by listing the repage_* tools you now have (repage_publish_document, repage_get_document, repage_update_document, repage_list_versions, repage_list_comments).

Prefer to do it by hand? Pick your tool above for click-by-click steps. All tools use the same server URL — https://www.repage.app/api/mcp — and authenticate through a Google sign-in flow, so there's no API key to manage.

What tools does the MCP server expose?

ToolWhat it does
repage_publish_documentCreate a new Repage document from HTML and get a shareable URL.
repage_get_documentFetch the current HTML source of a document you own.
repage_update_documentPublish new HTML as a new version of an existing document.
repage_list_versionsList the version history of a document.
repage_list_commentsRead comments teammates left on a document.

How authentication works

Repage uses standard OAuth 2.0 with PKCE. When you first add the server, your AI client discovers the auth endpoint automatically (via RFC 8414), opens a browser tab, and asks you to sign in with Google. The resulting token is stored locally by your client — you only do this once.

Prefer a static token? You can create an API key on your dashboard and pass it as an Authorization: Bearer <key> header instead.

Typical workflow

  1. Generate HTML
    Ask your AI to create a report, dashboard, PRD, or prototype as a complete HTML document.
  2. Publish
    Say “publish this to Repage”. The AI calls repage_publish_document and returns a link like https://www.repage.app/d/abc123.
  3. Share & collect feedback
    Send the link to teammates. They can view it and leave inline comments without any account.
  4. Revise
    Ask the AI to fetch the document (repage_get_document), make changes, then update it (repage_update_document). The URL stays the same; the old version is kept.

Ready to connect?

Publish your first document from inside your AI assistant.

Publish a document