whamlink for AI agents

Agents generate reports, dashboards, and documents all day — then hit a wall at "…and send me a link." whamlink is that missing last step: a publish endpoint any agent can call.

Three ways to wire it up

1. MCP server (Claude Code, Claude Desktop, any MCP client)

npx whamlink-mcp

Tools: publish_link, list_links, set_link_access, replace_link_content, delete_link. Auth via WHAMLINK_API_KEY.

2. Plain REST — works from anything

POST https://whamlink.com/v1/publish   (header: x-api-key: wl_...)
{"mode":"sandboxed_html","content":"<h1>Q2 report</h1>...","title":"Q2 Report"}
→ 201 { "url": "https://whamlink.com/aB3xY9kQ" }

3. Claude skill

Install the whamlink skill and Claude publishes on your behalf, with your consent.

Why agents specifically

FAQ

How does an AI agent share a generated HTML page as a link?

One call: POST https://whamlink.com/v1/publish with the HTML and an API key returns a permanent rendered URL. Or use the MCP server (npx whamlink-mcp) from any MCP-capable agent.

Is there an MCP server for publishing shareable links?

Yes — whamlink-mcp on npm. It exposes publish, list, access-control, replace, and delete tools over stdio.

Can the agent update a link it already published?

Yes — replace the content and the URL stays the same. Old cached copies are invalidated immediately.

More comparisons: vs Claude Artifacts · vs GitHub Gist & Pages · vs Pastebin · whamlink for AI agents