Turn Windsurf Cascade output into a link

Windsurf's Cascade agent produces plans, code reviews, release notes and migration checklists inside the editor — and that is where they stay. MintPage gives Cascade a publish_page tool, so the same output becomes a public URL you can drop into a pull request, a Slack thread or an email, without leaving Windsurf.

Connect Windsurf

Open Windsurf Settings → Cascade → Manage MCPs, click View raw config, and add MintPage under mcpServers. The file lives at ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "mintpage": {
      "serverUrl": "https://mintpage.ai/mcp",
      "headers": { "Authorization": "Bearer mp_your_key" }
    }
  }
}

Windsurf uses serverUrl (not url) for remote servers and infers the transport from it, so no type field is needed. Save the file, then press the Refresh button in Manage MCPs — Windsurf does not reload servers on its own. mintpage should appear with its tools listed. Then ask Cascade: "publish this review as a page and give me the link." It calls publish_page and returns a URL.

Leave out the headers block to use guest mode: no key, no account, pages last 24 hours. A free key from /start makes them last 7 days and unlocks stats; Pro ($5/month or $39/year) makes them permanent with custom slugs.

If you would rather keep the key out of the config file, Windsurf can read it from the environment: "Authorization": "Bearer ${env:MINTPAGE_KEY}". The key can also travel in the path instead of a header: "serverUrl": "https://mintpage.ai/mcp/mp_your_key". Either way, keep mcp_config.json out of version control.

Good uses

• Review before merge. Ask Cascade to review a diff, publish the review, and send one link to the author instead of pasting the editor pane into a comment.
• Onboarding notes. "Explain how this repository is organized, then publish it" gives new teammates a readable page rather than a chat transcript.
• Living status pages. Publish once, then update_page at the same URL after each run; the link in your PR description never goes stale.
• Client-facing summaries. A plain-English summary of what changed this week, published with the paper theme, reads well to people who will never open the editor.

Example call

{"name":"publish_page","arguments":{"title":"Auth service — code review","content":"# Review: auth service refactor\n\n**Verdict:** approve with two nits.\n\n- `refreshToken()` swallows the network error; log it.\n- Add a test for the expired-token path.","theme":"ink","byline":"Reviewed by Cascade in Windsurf"}}

What stays safe

Pages are public to anyone with the link, and the tool description tells the agent never to publish secrets. HTML is sanitized (no scripts, forms or iframes) and served with a strict Content-Security-Policy. Delete a page any time with delete_page.

FAQ

Does Windsurf support remote HTTP MCP servers? Yes. Any entry with a serverUrl is treated as a remote server; MintPage is plain streamable HTTP with no OAuth dance, so the URL plus an optional bearer header is the whole configuration.

Cascade says the server has no tools. Press Refresh in Manage MCPs after editing the config, or restart Windsurf. If it still shows nothing, check that the JSON is valid and that the header value starts with the literal Bearer .

Can Cascade update a page instead of making a new one? Yes: update_page keeps the URL and replaces the content, which is how a living status page works.

Is there a size limit? Guest pages up to 250 KB, free keys 1 MB, Pro 2 MB. Markdown and sanitized HTML are both accepted.

Which tools does the server expose? publish_page, update_page, list_pages, delete_page, get_page_stats, get_account and rotate_api_key.

Other ways in

The same server works from agent reports, ChatGPT, Claude.ai & Desktop, Claude Code, Codex CLI, Cursor, Gemini CLI, the Markdown API, VS Code. Full tool reference in the docs; live examples on the showcase.