dribbble-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for tool calls; without it a tool call answers: "Set COTLET_API_KEY. Get a key 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.
Dribbble through Cotlet.dev. Call dribbble_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 |
|---|---|
| dribbble_guideA | How to work in Dribbble (leads, client messages, Pro Analytics, shots and comments): its screens and the sign-in link. Call this first. |
| dribbble_statusA | Check that your Cotlet.dev account and Dribbble are ready: account, credits and Dribbble connection. |
| dribbble_openB | Open a Dribbble page in your signed-in Cloud Browser (default https://dribbble.com) to work with leads, client messages, Pro Analytics, shots and comments. |
| dribbble_readB | Read the current Dribbble page: its text and numbered buttons, links and fields. |
| dribbble_clickC | Click a numbered element on the current Dribbble page. |
| dribbble_typeB | Type text into a numbered field on the current Dribbble page. |
| dribbble_closeA | Close the Dribbble 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: onboarding guide, readiness check, browser opening, page reading, clicking, typing, and closing. There is little risk of confusing one tool with another because the browser interaction primitives are cleanly separated from setup/help tools.
All tools share the dribbble_ prefix and snake_case style, forming a predictable namespace. Most names are verbs, though guide and status are noun-like, which is a minor deviation from a strict verb_noun pattern.
Seven tools is well-scoped for a browser-session wrapper that needs setup, page reading, interaction primitives, and cleanup. Each tool appears to earn its place without obvious redundancy.
The toolset covers the core browser lifecycle: open, read, click, type, and close, plus guide and status for orientation and readiness. Minor interaction gaps such as scrolling or screenshot capture may exist, but the main Dribbble workflows are supported.