htmldrop runs a hosted MCP server at
https://htmldrop.app/mcp. Any MCP-capable assistant can connect to it and
publish on your behalf — you approve once in the browser, and no keys are ever
pasted into a chat.
The fastest setup
Paste this into your agent and it will configure itself from our machine-readable
instructions:
Or follow a per-client guide: ChatGPT ·
Claude · Claude Code ·
Codex · Cursor and Cline ·
CLI · CI and headless.
What the agent can do
Publishing to an existing slug updates that drop and keeps the URL, so “update my
portfolio and republish” works the way you would hope.
How authentication works
The remote server is OAuth-first. On the first tool call your browser opens, you
approve, and the client stores and refreshes tokens itself. Nothing to copy, and
you can revoke access at any time from the dashboard.
For environments with no browser — CI, containers, cron — use an API token
instead. See CI and headless.
The npm packages are scoped: @htmldrop.app/mcp and @htmldrop.app/cli. The
unscoped htmldrop package is an unrelated third-party project. If an assistant
suggests npx htmldrop, correct it.
