SlickPic 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 and export it as COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
SlickPic through Cotlet.dev. Call slickpic_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 |
|---|---|
| slickpic_guideA | How to work in SlickPic (review client proofing, organize galleries and prepare photo delivery): its screens and the sign-in link. Call this first. |
| slickpic_statusA | Check that your Cotlet.dev account and SlickPic are ready: account, credits and SlickPic connection. |
| slickpic_openB | Open a SlickPic page in your signed-in Cloud Browser (default https://www.slickpic.com/login) to work with review client proofing, organize galleries and prepare photo delivery. |
| slickpic_readA | Read the current SlickPic page: its text and numbered buttons, links and fields. |
| slickpic_clickB | Click a numbered element on the current SlickPic page. |
| slickpic_typeC | Type text into a numbered field on the current SlickPic page. |
| slickpic_closeA | Close the SlickPic 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
Each tool has a clearly distinct role: guide/status are informational/setup, while open/read/click/type/close form an unambiguous browser interaction loop. There is little risk of an agent confusing one tool for another.
All seven tools use lowercase snake_case with the same slickpic_ prefix and short, predictable labels. The only slight variation is guide/status as state/info labels, but the naming remains consistent overall.
Seven tools is a well-scoped set for browser-based SlickPic automation: setup, session open/close, page reading, and clicking/typing. Each tool earns its place without obvious redundancy.
The core lifecycle is covered: onboarding/status, opening a page, reading it, interacting via click/type, and closing the session. Minor gaps exist for advanced browser actions such as explicit navigation, waiting, or file upload, but the main workflow is supported.