picdrop MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Get one at https://cotlet.dev/app. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
picdrop through Cotlet.dev. Call picdrop_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| picdrop_guideA | How to work in picdrop (review client selections and compare image versions): its screens and the sign-in link. Call this first. |
| picdrop_statusA | Check that your Cotlet.dev account and picdrop are ready: account, credits and picdrop connection. |
| picdrop_openB | Open a picdrop page in your signed-in Cloud Browser (default https://www.picdrop.com) to work with review client selections and compare image versions. |
| picdrop_readA | Read the current picdrop page: its text and numbered buttons, links and fields. |
| picdrop_clickB | Click a numbered element on the current picdrop page. |
| picdrop_typeB | Type text into a numbered field on the current picdrop page. |
| picdrop_closeA | Close the picdrop browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools split cleanly into setup (guide, status, open) and page interaction (read, click, type, close), with descriptions that clarify when to use each. The three setup tools share the same domain phrasing ('review client selections and compare image versions'), so an agent must read the descriptions to distinguish guidance, account checks, and actual page opening.
Every tool uses the same picdrop_<action> pattern with short, unambiguous verbs (open, read, click, type, close, guide, status). The convention is predictable throughout and maps directly onto a browser-session lifecycle.
Seven tools is well within the ideal range for a browser-automation wrapper and each one earns its place in the open → read → act → close flow. Nothing feels redundant or missing from a count perspective.
The core interaction loop (open, read, click, type, close) plus guide/status covers basic navigation, but common browser needs are absent: no scroll, back/goto navigation, keyboard submit, screenshot, or file upload/download. For a picdrop workflow involving comparing image versions and reviewing client selections, the lack of any visual/image-capture capability is a notable gap.