Categories › Cloud & DevOps › Hosting & deployment
Publish micro-apps from your AI with no account; operate them as real apps. Data stored in the EU.
Remote server: your requests and data go to mcp.dropyour.io. Claude Code: claude mcp add --transport http dropyour https://mcp.dropyour.io/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
dropyour_whoami — Check how this session is authenticated: resolved tier (anonymous / free / pro) and its limits. Call this after configuring an account tokendropyour_publish — Publish a self-contained HTML file to Dropyour. Returns a stable public URL (one origin per drop — same address across updates, browser datadropyour_publish_system — Publish 1 to 5 apps in ONE call, each at its own stable URL, all managed by ONE system token (ADR-0352). No account needed. Each app is a sedropyour_replace — Replace the content of an existing drop — HTML, or a base64 .zip once the app has GRADUATED to tier 4. The URL never changes (origin contracdropyour_update_settings — Change a drop's visibility (private = link-only + noindex, public = indexable), its expiration, or remove the "Hosted on Dropyour" badge (badropyour_secret_set — Store a SECRET for a graduated app (tier 4), bound to a host pattern. The value is encrypted at rest and NEVER readable back — by anyone, evdropyour_secret_delete — Delete a secret from a graduated app's vault by name. Deleting a name that does not exist is not an error — the final state is what you askedropyour_logs — Read a graduated app's own log buffer (tier 4): the last 200 lines, most recent first — explicit `app.log(...)` calls from the app's server dropyour_egress_deny — Cut a host your graduated app is calling — in ONE call, taking effect on the next request, with NO republish. This is the verb for the momendropyour_secrets_list — List a graduated app's secrets: NAMES, host bindings, dates and how each key is attached (form) only — values are never returned, by design dropyour_graduate — GRADUATE one of your drops to tier 4 — a real backend (server code, queryable store, isolated SQLite) behind the SAME URL, with its data cardropyour_import — Bring an EXISTING app to Dropyour in one call: zip its files (you have them — from GitHub, disk, another host) and pass the archive. A singldropyour_read_app_files — Read what a GRADUATED app actually SERVES right now — not the seed captured before it graduated. Without path: the list of files in the servdropyour_call — Call a route of YOUR OWN drop and get the real HTTP answer back: status, headers, duration, body. This is how you check that what you just pdropyour_schedule — Your app's clock, in one verb. action='read' (default) tells you when it next rings, whether the app is frozen, and the last runs WITH THEIRdropyour_status — Get a drop's status: URL, visibility, expiration, size, approximate view count, and its private name (if set). With an account token, owned dropyour_read_content — Read a drop's source HTML (what you published — no shared-memory shim, no attribution badge). For multi-file sites, also returns the list ofdropyour_read_data — Read a drop's app data — the shared-memory state (a JSON key/value snapshot mirroring the app's localStorage), so you can answer questions adropyour_write_data — Write a drop's app data — replace the shared-memory state (the JSON key/value object mirroring the app's localStorage), so you can update whdropyour_list_versions — List the published versions of a GRADUATED app (level 4), newest first, with the one currently served. Each version carries its network and dropyour_rollback — Roll a GRADUATED app back to a previously published version — this is the EXPECTED FAILURE PATH of dropyour_release, which calls it for you dropyour_milestone — A milestone records the version currently SERVED by every GRADUATED app of the anchor's system (dropyour_system), callers first; when the andropyour_records_summary — Summarise what a GRADUATED app keeps in its queryable store: one line per collection with the number of records and the bytes they occupy. Ndropyour_records_list — Read one page of a collection from a GRADUATED app's queryable store, most recently updated first. Pass the returned cursor to get the next dropyour_autonomy — Declare how much you delegate to the machine on ONE of your apps. Three modes. Loosening the ceiling, or going back to 'copilote' from a deldropyour_link — Let one of your graduated apps call ANOTHER of your apps over the network. By default no app can reach another — that refusal is the platfordropyour_rotate_token — Mint a NEW management token for a drop and kill the old one — the self-serve way out of a lost or leaked token. With the old token it goes tdropyour_patch — Replace ONE literal anchor in the SERVED content without re-uploading everything — the Edit semantics you already know. old = the exact litedropyour_app_tools — Make YOUR graduated app callable by a third party's agent, as an MCP server at https://<dropId>.dropyour.site/mcp — live as soon as ONE tooldropyour_events — Events between YOUR server apps, SIGNAL ONLY. A topic (e.g. 'devis.signe') declares the identifier keys its signal carries, e.g. ['devisId']dropyour_records_visibility — Declare the visibility of ONE collection of your graduated app's store. Two values, no policy language. 'partagee' (the default): all in-appdropyour_records_write — Write (or replace) ONE row in a graduated app's store, without republishing anything. The store is the app's queryable database (tier 4); thdropyour_release — Publish new content AND check it works, in one transaction. If any check fails, the previous version is put back automatically and you get tdropyour_domain — Serve an app under the owner's own domain (Pro: three domains per account, subdomains included: app.example.com and blog.example.com count adropyour_support — Read Dropyour support's diagnosis for one of the account's apps: the typed facts (publication refusals, activity, health, versions, domain, dropyour_support_report — Report to Dropyour a defect of the PLATFORM that dropyour_support diagnosed (side: platform, reportable: true). This WRITES: one report per dropyour_delete — Permanently delete a drop. Final — the URL is never reassigned. With a management token it is immediate. With a connected account or an accodropyour_delegate — Let ANOTHER Dropyour account maintain one of your apps, with a closed role, and take it back at any time. Granting: a human confirms it: witdropyour_decision — Write down a structural decision you made for one of the owner's SERVER apps (graduated), in plain text: why (context), what (decision), whadropyour_system — Manage SYSTEMS: named groups of up to 9 of your apps, handled as one (ADR-0353). action='list' (default) shows your systems and their apps. Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.