Artidrop publishes HTML, Markdown and multi-file sites as shareable URLs, and lets an assistant look up artifact metadata, content and version history.
What you can do
Publish HTML or Markdown content as a shareable URL, passing the source byte-for-byte so inline scripts keep working. Publish a multi-file HTML site from a base64-encoded ZIP that has an index.html at its root. Retrieve artifact metadata, optionally including the full HTML content. List the version history of an artifact.
When to use it
Useful when you want an assistant to turn a generated page, document or small static site into a link you can share, and to check what was published and which versions exist.
Requirements
A remote MCP endpoint at artidrop.ai over streamable HTTP; no packages, environment variables or headers are declared. Very large content or sites already on disk are better sent through the service's REST upload endpoint.
Before you install
Publishing makes content available at a shareable URL, so anything sent becomes externally reachable; avoid publishing secrets or private data. Published artifacts can be retrieved with their full HTML content and version history is retained.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.artidrop%2Fartidrop/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Publish HTML or Markdown content as a shareable URL. Pass `content` byte-for-byte from the source — do not retype, reformat, minify, summarize, or 'clean up' the input; even one stray character can break inline scripts on the published page. If the content is too large to copy verbatim through the model, use the REST endpoint `POST /v1/artifacts` (or `/v1/artifacts/upload` for ZIPs) instead. For Markdown, optionally include images as base64-encoded data.
Publish a multi-file HTML site from a base64-encoded ZIP file. The ZIP must contain an index.html at its root. For sites larger than ~10MB — or whenever you have the file on disk — prefer the REST API /v1/artifacts/upload endpoint to avoid base64 overhead and to guarantee byte-faithful upload.
Parameterstitlevisibilityzip_base64required
get
Get artifact metadata. Set include_content to true to also return the full HTML content.
Parametersidrequiredinclude_content
versions
List version history of an artifact
Parametersidrequired
Version history
1
v1.1.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.