HTMLRadar · MCP
Publish the HTML your agent just wrote as a tracked link.
Updated August 2026
The HTMLRadar MCP server gives any agent — Claude Code, Cursor, Codex — one tool that turns an HTML deck, proposal or report into a tracked link, and a second tool that reports who opened it, how long they read, and which sections held them. Free for two links, then $15 a month. AGPL-3.0.
Your agent writes an HTML deck. You send it. Then nothing — you have no idea whether it was opened. This closes that loop without leaving the terminal.
The one thing other publish-from-agent servers do not do
There are plenty of MCP servers that will put a file on the internet and hand back a URL. That is the easy half. The half that matters is the next morning, when you want to know whether the person you sent it to actually read it.
HTMLRadar is the one where the agent can ask. “Did anyone read the proposal I shared yesterday?” returns a real answer: opened at 14:02, four minutes of active reading, 87% scroll depth, two minutes forty on The Ask, skipped Market sizing.
Install
First create an API key at htmlradar.com/settings under API keys. Keys start with hr_live_.
Claude Code
Put the key in your environment first. A key passed as a literal argument stays in your shell history, and on most systems it is visible in the process list to anyone else on the machine.
export HTMLRADAR_API_KEY=hr_live_… claude mcp add htmlradar -e HTMLRADAR_API_KEY=$HTMLRADAR_API_KEY -- npx -y htmlradar-mcp
Or install the plugin, which adds the server plus a skill that teaches Claude when to offer a tracked link. It reads the same environment variable, so there is nothing to paste:
/plugin marketplace add htmlradar/htmlradar /plugin install htmlradar@htmlradar
The literal form works too — -e HTMLRADAR_API_KEY=hr_live_xxx — and is fine for a throwaway key you are about to revoke.
Cursor
{
"mcpServers": {
"htmlradar": {
"command": "npx",
"args": ["-y", "htmlradar-mcp"],
"env": { "HTMLRADAR_API_KEY": "${env:HTMLRADAR_API_KEY}" }
}
}
}Cursor expands ${env:NAME} inside env, which keeps the key out of a file you might commit. A literal hr_live_… there also works.
Codex CLI
export HTMLRADAR_API_KEY=hr_live_… codex mcp add htmlradar --env HTMLRADAR_API_KEY=$HTMLRADAR_API_KEY -- npx -y htmlradar-mcp
npm publish is pending. Until htmlradar-mcp is on npm, clone the repository, run pnpm install && pnpm --filter ./packages/mcp build, and replace the launch command with node /path/to/htmlradar/packages/mcp/dist/index.js.
Three tools
| Tool | Does | Detail |
|---|---|---|
| share_html | Publish HTML as a tracked link | Takes the markup itself or a path to a .html file, plus optional recipient label, email gate, password, allowed email domains, expiry and custom link name. Returns the tracked link, the dashboard link and the share id. |
| get_share_activity | Ask whether it was read | Takes a share id. Reports whether the link was opened, by whom, when, how long they actively read, how far they scrolled, and which sections took the most time. |
| whoami | Check the account and plan | Reports which account the key belongs to, the plan it is on, and how many free tracked links are left. |
You do not call them by name. You say what you want:
share this deck with acme as a tracked link, email gate on did anyone read the proposal I shared yesterday?
Common questions
- What does the HTMLRadar MCP server do?
- It gives your agent two abilities: publish an HTML document as a tracked link, and read back who opened that link, how long they stayed, and which sections held their attention. It is a stdio MCP server that works with Claude Code, Cursor, Codex CLI, and any other MCP client.
- How is this different from other publish-from-an-agent MCP servers?
- Most of them stop at returning a URL. HTMLRadar keeps the other half of the loop: the agent can ask, the next day, whether the recipient read what you sent and which sections they spent time on. That question is the reason the server exists.
- Do I need an API key?
- Yes. Sign in at htmlradar.com, open Settings, and create a key under API keys. Pass it to the server as the HTMLRADAR_API_KEY environment variable rather than as a literal command-line argument, so it stays out of your shell history. The server reads nothing else and sends no telemetry.
- What does the recipient see?
- The document, exactly as written, behind an email prompt unless you turn the gate off. They never see the tracking, the dashboard, or anyone else who opened the link. HTMLRadar stores no raw IP address, no keystrokes, no mouse positions and no session replay.
- What happens when the free links run out?
- The free tier covers two tracked links. After that the share_html tool returns an upgrade message instead of a link, and the agent is instructed to relay it to you rather than retry. Pro is $15 a month or $150 a year for unlimited links.
- Can I point it at my own instance?
- Yes. HTMLRadar is AGPL-3.0 end to end. Set HTMLRADAR_API_URL to your own deployment and the server talks to that instead of htmlradar.com.
First 2 tracked links free. No credit card. AGPLv3 source on GitHub.