The HTML report MCP server your agent already knows how to call
Wire CastHTML Remote MCP into Claude Code, Cursor, VS Code, Codex, or Windsurf once — then every conversation can call publish_report the moment an artifact is ready. One second later, a double-sandboxed /r/{slug} link is ready to share.
Verified registry & live inspector
Paste your cast_live_... token into the RemoteMCP.net Online Inspector to test the handshake live, or visit the verified registry entry for setup guides across the 10 most popular MCP clients. The machine-readable server card lives at /.well-known/mcp.json.
One-line setup for every client
# Claude Code
claude mcp add --transport http casthtml https://casthtml.com/mcp \
--header "Authorization: Bearer cast_live_YOUR_KEY"
# Cursor — ~/.cursor/mcp.json
{
"mcpServers": {
"casthtml": {
"type": "http",
"url": "https://casthtml.com/mcp",
"headers": { "Authorization": "Bearer cast_live_YOUR_KEY" }
}
}
}
# VS Code — .vscode/mcp.json
{
"servers": {
"casthtml": {
"type": "http",
"url": "https://casthtml.com/mcp",
"headers": { "Authorization": "Bearer cast_live_YOUR_KEY" }
}
}
}
# OpenAI Codex — ~/.codex/config.toml
[mcp_servers.casthtml]
url = "https://casthtml.com/mcp"
bearer_token = "cast_live_YOUR_KEY"
Five tools, clearly annotated
Every tool carries standard MCP annotations so clients can reason about safety before calling them — publish Claude artifacts via MCP, or share a Markdown report through the same MCP connector.
| Tool | Purpose | Read-only | Destructive | Idempotent | Open-world |
|---|---|---|---|---|---|
publish_report | Publish HTML, Markdown, or a report to get a /r/{slug} link | — | — | — | ✓ |
update_report | Update an existing report in place by id or slug | — | — | ✓ | ✓ |
list_reports | List the 50 most recent reports on the account | ✓ | — | ✓ | — |
get_report | Fetch metadata and text content of a report by id or slug | ✓ | — | ✓ | — |
delete_report | Delete a report immediately; the link stops working | — | ✓ | ✓ | — |
Why publish through MCP instead of copy-paste
Zero context switch
The conversation ends with a link, not a clipboard. The agent calls publish_report and hands you the URL.
Iterate under one link
update_report edits in place — "tweak the colors and republish" keeps the same URL for everyone you already shared it with.
Scoped credentials
cast_live_ keys only reach report APIs — never billing, admin, or key management — and can be revoked instantly.
Sandboxed by default
Everything the agent publishes renders inside a strict iframe sandbox with CSP lockdown, safe to forward to anyone.
Frequently asked questions
What is the CastHTML Remote MCP server?
It is a native streamable-HTTP MCP endpoint at https://casthtml.com/mcp that lets MCP clients — Claude Code, Cursor, VS Code, Codex, Windsurf — publish, update, list, read, and delete CastHTML reports directly from the conversation.
How do I get an API key for the MCP server?
Sign in to CastHTML, open the History page, and use the "API & MCP Integration" panel to mint a cast_live_ key. Keys are shown once, can be revoked at any time, and authenticate via the Authorization: Bearer header.
Is the MCP server safe to expose to an agent?
The key only reaches report APIs — it cannot manage API keys, billing, or admin surfaces. Reports publish inside a locked-down iframe sandbox by default, and quota, rate limits, and Pro checks apply to MCP calls exactly as they do in the browser.
Can the agent update a report it already published?
Yes — update_report accepts a report id or slug and edits in place, so the share link stays stable while the agent iterates on content, title, or settings.
Where can I verify the server handshake before wiring a client?
Use the RemoteMCP.net online inspector with your cast_live_ token, or check the server card at casthtml.com/.well-known/mcp.json for the machine-readable description of transports, auth, and capabilities.