Publish HTML from Claude Code — live in seconds.

Add htmldrop's hosted MCP server with one command, ask Claude Code to publish, and get a live shareable URL back. No API keys, no config files, no build step.

claude mcp add --transport http htmldrop https://htmldrop.app/mcp

No API key to create, paste, or rotate. The first tool call opens a sign-in page in your browser — approve it once and you're done.

Install details

1. Add the remote MCP server. Run the command above. Claude Code registers https://htmldrop.app/mcp as a remote (streamable HTTP) server — confirm it with claude mcp list.
2. Sign in when the browser opens. The first htmldrop tool call starts an OAuth sign-in in your browser. Approve it once; Claude Code holds a short-lived token and refreshes it for you, and no credential is written to a config file.
3. Publish. Ask Claude Code to publish your HTML or Markdown — it calls htmldrop_publish and hands back the live slug.htmldrop.app URL.

Try it

Open Claude Code's chat and try any of these:

CI, scripts, and headless environments

Automation can't complete a browser sign-in, so there's a second path: the npm stdio server, authenticated with an API token. Use it for CI jobs, cron scripts, and the rare client that can't reach a remote MCP server — not for everyday work in Claude Code.

# Inject the token from your CI secrets or OS keychain — never a literal in a file
export HTMLDROP_API_TOKEN="<your token — from dashboard, store in a secret manager>"
npx -y @htmldrop.app/mcp

Create the token at htmldrop.app/dashboard/settings → API tokens; it's shown once and carries full access to your account. Never commit the literal value to a repository or paste it into a config file you'll check in — reference it from your secret store, and revoke it from the dashboard the moment it may have leaked.

Troubleshooting

The sign-in page never opened

Claude Code launches your system's default browser. If nothing appears, check that a default browser is set, then copy the authorization URL Claude Code prints and open it by hand. Over SSH or in a container there's no browser to open — use the CI path above instead.

Signed in, but the tools still fail

The stored authorization has gone stale. Remove and re-add the server to run a fresh sign-in: claude mcp remove htmldrop, then the claude mcp add command above.

Claude Code doesn't see the htmldrop tools

Run claude mcp list to confirm htmldrop is registered and connected. If it shows red, run claude mcp logs htmldrop for details — a blocked or unreachable https://htmldrop.app/mcp (corporate proxy, offline) is the usual cause.

"No API token" error

This one only applies to the CI path above — the remote server never asks for a token. Verify HTMLDROP_API_TOKEN resolved to the token string from your secret store (not the friendly name you gave the token in the dashboard, and not an empty variable).

"plan_limit" error in the chat

You've hit your plan's site cap (3 active drops on Free). Delete a drop in the dashboard or upgrade.

Want to verify the install worked?

In Claude Code chat: "List my htmldrop sites." If the tool is wired up, Claude Code calls htmldrop_list and replies with your drops.