Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Dropl is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
9
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
Create client-editable photo and video galleries from Cursor or Claude Code, then embed them.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user dropl-mcp '--' npx -y @dropl/mcp
# 2 — ask your agent for something these tools do
# whoami, list_sites, create_site and 35 more
Dropl costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DRAll 1 server
dropl1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Dropl as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user dropl-mcp '--' npx -y @dropl/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take DROPL_API_KEY (Optional. Dropl API key; overrides the saved browser sign-in.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
38 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Shows the connected Dropl account, user, role, and API key (name, prefix, scopes, site restriction) plus the web app URL. Use it first in a session to confirm which account you're acting on, or when another tool reports a sign-in or permission error. Needs a saved sign-in or DROPL_API_KEY; it…
No parameter schema on file.
Lists the client sites (one per client website) this connection can reach, with their domains and the plan's site allowance. Use it before creating anything, to find the site id for the client the user means and avoid duplicate sites. Keys restricted to some sites only see those sites.
No parameter schema on file.
Creates a client site: the home for one client website's showcases, videos, collections, and feedback. Use it when the client has no site yet; check list_sites first to avoid duplicates. Only call after showing the plan to the user and getting explicit confirmation. Counts toward the plan's site…
No parameter schema on file.
Lists a client site's showcases (embeddable photo and video galleries), newest first, with their type (gallery or projects) and item and project counts. Use it to reuse an existing gallery or portfolio instead of creating a duplicate, or to find a showcase id. Paged: pass nextCursor to get more.
No parameter schema on file.
Creates a showcase: an embeddable photo/video gallery the client can update from their phone. Use it when the user wants a gallery, portfolio, project photos, or a section the client can update themselves. Requires a site id from list_sites or create_site. Only call after showing the plan to the…
No parameter schema on file.
Summarizes a showcase: type, settings, item counts by status (processing/ready/failed) and kind, project counts and details (projects showcases), categories with counts, photos without alt text, and failed items. Use it to check that an upload finished processing or to review a gallery before…
No parameter schema on file.
Pages through a showcase's items in display order: id, kind, status, file name, the local path it was uploaded from, alt text, and categories. Use it to find item ids for update_items or tag_items, or photos that still need alt text (missingAlt: true). Up to … items per call; local paths only…
No parameter schema on file.
Sets alt text and adds/removes categories on many showcase items in one call. Use it after an upload to fix alt text or categories by id (files[].id from upload_photos / upload_videos, library video ids, or ids from list_showcase_items) instead of uploading again. Up to … items per call; category…
No parameter schema on file.
Changes a showcase's title, layout, grid fit, category filter tabs, or items per page. Use it when the user wants the gallery to look or page differently; embeds pick up the change without new code. Pass only the settings to change; at least one is required.
No parameter schema on file.
Adds a category (a filter tab) to a showcase. Use it to group items, e.g. one category per project type or source folder, before tagging them; upload and tagging tools also create missing categories by name. If one with the same name or slug exists, it's returned instead of creating a duplicate.
No parameter schema on file.
Adds and/or removes the same categories on many showcase items (photos or videos) at once. Use it to put uploaded items into filter tabs, with itemIds from upload_photos / upload_videos (files[].id; library video ids work too) or list_showcase_items. Up to … items per call; category names that…
No parameter schema on file.
Uploads local photos (JPEG, PNG, WebP, AVIF, HEIC; up to 20 MB each) into a showcase, straight to storage. Use it to turn a folder of project photos into a client-editable gallery: pass files, folders (recursive by default), and globs via paths, and per-photo alt text and categories via files.…
No parameter schema on file.
Lists videos in a client site's library (newest first), optionally filtered by a title search. Use it to find video ids for get_embed_code or add_videos_to_showcase, or to check a video is already hosted before uploading it again. Paged: pass nextCursor for more.
No parameter schema on file.
Uploads local videos (MP4, MOV, WebM, MKV, AVI, MPEG, M4V) to a client site's video library in resumable parts, titled from their file names, for streaming playback without YouTube or Vimeo. Use it to host a hero video or a folder of clips; with showcaseId it also adds them to that showcase (and…
No parameter schema on file.
Adds existing library videos to a showcase, or to one project of a projects showcase. Use it for videos already hosted in Dropl (ids from list_videos or upload_videos) instead of uploading them again. Videos must belong to the showcase's client site; ones already in it are skipped.
No parameter schema on file.
Returns the official embed snippet for a video (videoId) or a showcase (showcaseId, optionally one category by name or slug, or one project's page), plus where and how to paste it (plain HTML, React/Next.js, WordPress, Webflow, Framer). Use it whenever a gallery, portfolio, or video goes onto a…
No parameter schema on file.
Shows storage and bandwidth used against the plan's limits this period, and whether uploads or playback are suspended. Use it before a large upload, or when the user asks how much space is left. Figures cover the whole account, not one client site.
No parameter schema on file.
Scans a local folder without uploading and proposes how to bring it into Dropl: top-level folders become categories (or, for a portfolio, projects), photo/video counts and sizes per folder, unsupported files by reason, upload batches, whether it needs several showcases, remaining storage, and the…
No parameter schema on file.
Lists a projects showcase's projects in order: slug, title, subtitle, a description excerpt, detail values by key, categories, and item counts. With project, it returns that project's full description, labeled details, and its photos and videos in order (ids, local paths, alt text). Use it to find…
No parameter schema on file.
Creates a project at the end of a projects showcase: title, subtitle (e.g. type and location), description, detail values by key, and categories. Use it for each job in a portfolio, then upload its photos with upload_photos and project. Only call after showing the plan to the user and getting…
No parameter schema on file.
Changes a project's title, subtitle, description, slug, detail values, categories, or cover photo. Use it to fill in or correct a project, e.g. with details from the old site. Pass only what changes: details merge (null clears one), categories replace the project's categories, and a new title…
No parameter schema on file.
Sets the order of a projects showcase's projects on the website. Use it when the user wants projects in a specific order, e.g. newest or featured first. Pass projects in the new order; ones you leave out keep their current order after them.
No parameter schema on file.
Sets the order of the photos and videos inside one project. Use it to choose which photos lead a project page (the cover is set with update_project). Pass item ids in the new order (from list_projects with project; library video ids work too); ones you leave out keep their current order after them.
No parameter schema on file.
Reads the details a projects showcase defines for every project (facts like location, year, or square footage): each detail's key, label, type, unit, options, and whether it shows on cards, plus the version plan_project_details needs. Use it right before changing details or filling in values,…
No parameter schema on file.
Dry run: previews changing a projects showcase's details to the full list you pass and returns a plain-text summary, with changes that remove project values marked destructive. Use it whenever the user wants to add, rename, reorder, or remove project details; nothing is saved. … … Show the summary…
No parameter schema on file.
Saves a change to a projects showcase's details: exactly the fields and expectedVersion you passed to plan_project_details. Use it once the user approved that plan. Only call after showing the plan to the user and getting explicit confirmation. It's refused (SCHEMA_CHANGED) when someone changed…
No parameter schema on file.
… Use it to find a collection id (a menu, inventory, team, or events) before reading or changing one, and to reuse an existing collection instead of creating a duplicate. Trashed collections only appear with trashed: true.
No parameter schema on file.
… Use it right before any change to a collection or its items, since clients and teammates edit in the dashboard. It returns the schemaVersion that plan_collections needs to change an existing collection.
No parameter schema on file.
… Use it whenever the user wants content their client can edit (a menu, inventory, events, team) or a field change; nothing is saved. Show the summary to the user before apply_collection_plan.
No parameter schema on file.
… Use it with exactly the collections you passed to plan_collections, once the user approved that plan. Only call after showing the plan to the user and getting explicit confirmation.
No parameter schema on file.
… Use it to move a hard-coded list (a menu array in a component, rows from a CSV) into a collection. Run with dryRun: true (the default) first; saving (dryRun: false) needs explicit confirmation. Accepts up to … items, sent in batches; retrying the same call doesn't duplicate items.
No parameter schema on file.
… Use it to check what's already in a collection before importing, or to find items. Up to … items per call; page with offset.
No parameter schema on file.
… Use it when wiring a page to read a collection, instead of guessing the response shape. Only published items reach the website.
No parameter schema on file.
… Use it when the user wants to revert a field or collection change. Only call after showing the plan to the user and getting explicit confirmation.
No parameter schema on file.
Lists feedback the client left on their website (comments on elements, text changes, general notes), newest first. Use it when the user asks to fix, review, or triage client feedback or change requests. Defaults to open and in progress. … Use get_feedback for the full context of one request.
No parameter schema on file.
Gets one feedback request with its full context: page URL, the clicked element (CSS selector, tag, nearby text, position), device and viewport, screenshot and photo URLs, and the thread. Use it before changing code for a request. … … Screenshot and photo URLs are temporary; fetch them to look.
No parameter schema on file.
Replies in a feedback request's thread as the signed-in user; the client gets the reply by email. Use it to ask the client to clarify, or to tell them what changed. … Keep replies short and plain (no code). Safe to retry: the same reply isn't posted twice.
No parameter schema on file.
Sets a feedback request to open, in_progress, done, or wont_do. Use it after fixing a request (done) or deciding not to (wont_do). … Marking done emails the client; only mark done once the fix is in the code (and deployed, if the user says so).
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Dropl or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.7.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest786f1cdadf581811cb00765047371a23469950db3f175b909000d9e6408226a7
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (38 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| whoami | no tags | |
| list_sites | no tags | |
| create_site | state-write | state-write: declares readOnlyHint: false |
| list_showcases | no tags | |
| create_showcase | state-write | state-write: declares readOnlyHint: false |
| get_showcase | no tags | |
| list_showcase_items | no tags | |
| update_items | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_showcase | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_category | state-write | state-write: declares readOnlyHint: false |
| tag_items | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| upload_photos | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_videos | no tags | |
| upload_videos | state-write | state-write: declares readOnlyHint: false |
| add_videos_to_showcase | state-write | state-write: declares readOnlyHint: false |
| get_embed_code | no tags | |
| get_usage | no tags | |
| plan_migration | no tags | |
| list_projects | no tags | |
| create_project | state-write | state-write: declares readOnlyHint: false |
| update_project | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| reorder_projects | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| reorder_project_items | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_project_details | no tags | |
| plan_project_details | no tags | |
| apply_project_details | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_collections | no tags | |
| get_collection_schema | no tags | |
| plan_collections | no tags | |
| apply_collection_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| add_collection_items | state-write | state-write: declares readOnlyHint: false |
| list_collection_items | no tags | |
| get_collection_code | untrusted-input | untrusted-input: keyword "fetch" |
| undo_collection_change | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_feedback | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_feedback | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| reply_to_feedback | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_feedback_status | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest786f1cdadf581811
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.0. Pin a release below and the command asks for exactly that one.
0.7.0
5 Oct 2026
latestNo release note was published with this version.
0.6.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Dropl can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.