# Dribbble API and MCP server

> Dribbble has a public API v2, but it covers only your own profile, shots, attachments, projects and job listings (checked 11 Oct 2026). Messages, leads, comments and Pro Analytics are not in it.

Community and marketplace where designers post their work as shots and get hired by clients for paid projects.

## What is the Dribbble API?

Cotlet's Dribbble API exposes 11 endpoints for your own Dribbble account: list shots, get shot stats, get Pro Analytics, list conversations, get conversation, list leads, list comments, upload shot, update shot, reply to message and reply to comment. The list_shots endpoint returns your shots, newest first, with title, tags, publish date and URL. Each endpoint takes simple JSON inputs like shot_id, limit or cursor and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 11 (7 read, 4 write)
- **Updated:** 2026-10-11

Dribbble has a public API v2, but it covers only your own profile, shots, attachments, projects and job listings (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Dribbble with 11 endpoints (7 read, 4 write): your AI agent signs in as you and does the work.

## Does Dribbble have an official API?

Dribbble has a public API v2, but it covers only your own profile, shots, attachments, projects and job listings (checked 11 Oct 2026). Messages, leads, comments and Pro Analytics are not in it.

| Task | Dribbble official | Cotlet |
|---|---|---|
| List your shots | Yes: GET /user/shots in API v2 | Yes |
| Upload a shot | Partly: Upload scope; GIF, JPG or PNG of exactly 400x300 or 800x600, up to 8 MB; no video | Yes |
| Edit a shot title, description and tags | Yes: PUT /shots/:id with the upload scope | Yes |
| Shot views, likes and saves | No: Shown in Pro Analytics; the API shot object has no such fields | Yes |
| Pro Analytics: leads, response rate, earnings | No | Yes |
| Read and reply to Messages | No | Yes |
| List Project and Service Requests | No | Yes |
| Reply to comments on your shots | No | Yes |

Sources: [Dribbble API v2 documentation](https://developer.dribbble.com/v2/), [Dribbble API v2: Shots](https://developer.dribbble.com/v2/shots/), [Dribbble help: About the Dribbble API](https://help.dribbble.com/en/articles/11065925-about-the-dribbble-api), [Dribbble help: Understanding your analytics](https://help.dribbble.com/en/articles/12141231-understanding-your-analytics)

## For AI agents

```text
Dribbble has a public API v2, but it covers only your own profile, shots, attachments, projects and job listings (checked 11 Oct 2026). Messages, leads, comments and Pro Analytics are not in it.
Cotlet provides a hosted MCP server and REST API for Dribbble: 11 tools (7 read, 4 write).
Access       Request access at https://cotlet.dev/app/signup?app=dribbble; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/dribbble
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_shots, get_shot_stats, get_pro_analytics, list_conversations, get_conversation, list_leads, list_comments, upload_shot, update_shot, reply_to_message, reply_to_comment
Confirm      upload_shot, reply_to_message, reply_to_comment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/dribbble-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=dribbble (Dribbble is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Dribbble once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Dribbble server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Dribbble MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Dribbble in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Dribbble's terms; Cotlet is not affiliated with Dribbble.
```

## What can an AI agent do in Dribbble?

Cotlet is best for freelance designers and small studios on Dribbble who want their AI agent to answer client requests, track leads and Pro Analytics, and reply to comments without running or fixing a server.

- **[Answer Project Requests and client messages](https://cotlet.dev/integrations/dribbble-api-mcp-server/answer-project-requests)** (runs: daily): "Go through my Dribbble Project Requests and unread messages from this week. Draft a reply or a polite decline for each one I have not answered, and show me every draft before it is sent." → `list_leads`, `list_conversations`, `get_conversation`, `reply_to_message`
- **[Weekly Pro Analytics report with top shots](https://cotlet.dev/integrations/dribbble-api-mcp-server/weekly-pro-analytics-report)** (runs: weekly): "Every Monday, send me my Dribbble Pro Analytics for the last 30 days compared with the 30 days before, plus which shots from the last month got the most saves." → `get_pro_analytics`, `list_shots`, `get_shot_stats`
- **Find leads you have not answered** (runs: daily): "Did any project requests come in this week that I have not answered yet?" → `list_leads`, `get_conversation`, `reply_to_message`
- **Find your best performing shots** (runs: weekly): "Which of my last 12 shots got the most saves? Put them in a table with views and likes." → `list_shots`, `get_shot_stats`
- **Reply to comments on your shots** (runs: daily): "Reply with a short thank you to every new comment on my latest shot." → `list_shots`, `list_comments`, `reply_to_comment`

## Can Dribbble automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Dribbble connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to answer project requests and client messages, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/dribbble/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/dribbble/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/dribbble/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/dribbble/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Dribbble.

### list_shots

Your shots, newest first, with title, tags, publish date and URL. Access: read. REST: `POST /api/v1/dribbble/list_shots`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | 1 to 100. Default: 24. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns your own shots, newest first, the same order as your profile. Each item has the title, tags, publish date and URL. Use the shot_id of an item in get_shot_stats, list_comments and update_shot. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "shots": [
    {
      "shot_id": "21847531",
      "title": "Fintech dashboard",
      "tags": [
        "ui",
        "fintech",
        "dashboard"
      ],
      "published_at": "2026-10-08T09:30:00Z",
      "url": "https://dribbble.com/shots/21847531-Fintech-dashboard"
    },
    {
      "shot_id": "21790442",
      "title": "Onboarding flow",
      "tags": [
        "ux",
        "mobile"
      ],
      "published_at": "2026-09-30T14:10:00Z",
      "url": "https://dribbble.com/shots/21790442-Onboarding-flow"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjI0fQ"
}
```

### get_shot_stats

Views, likes, saves and comment count of one of your shots. Access: read. REST: `POST /api/v1/dribbble/get_shot_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shot_id` | string | yes | Shot ID from list_shots. |

Returns the engagement numbers Dribbble shows for one of your shots: views, likes, saves and the number of comments. It works for your own shots only. The numbers are the ones Dribbble shows at the time of the call.

Example response:

```json
{
  "shot_id": "21847531",
  "title": "Fintech dashboard",
  "views": 4120,
  "likes": 186,
  "saves": 74,
  "comments": 12
}
```

### get_pro_analytics

Pro Analytics: leads, proposals, funded projects, response time and rate, conversion and earnings. Access: read. REST: `POST /api/v1/dribbble/get_pro_analytics`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `period` | enum | no | 30d, 60d, 90d or all_time. Default: 30d. |

Returns the figures of your Pro Analytics dashboard for a period: leads, project proposals, funded and completed projects, average project value, response time, response rate, lead conversion rate, cancellation rate and earnings. Dribbble refreshes these once a day. Needs a Pro account.

Example response:

```json
{
  "period": "30d",
  "leads": 14,
  "project_proposals": 6,
  "funded_projects": 3,
  "completed_projects": 2,
  "average_project_value": 2400,
  "response_time_hours": 3.5,
  "response_rate": 92.9,
  "lead_conversion_rate": 21.4,
  "cancellation_rate": 0,
  "earnings": 4800,
  "currency": "USD"
}
```

### list_conversations

Your Messages inbox: who, last message, time and whether it is unread. Access: read. REST: `POST /api/v1/dribbble/list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unread_only` | boolean | no | Only conversations with unread messages. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists your Dribbble Messages conversations, most recent first, with the other person, a preview of the last message, its time and whether it is unread. Set unread_only to see only what needs an answer. Pass conversation_id to get_conversation or reply_to_message.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "8841207",
      "with": "Marta Kowal",
      "last_message": "Hi! We need a redesign of our analytics dashboard.",
      "updated_at": "2026-10-10T08:14:00Z",
      "unread": true
    }
  ],
  "next_cursor": null
}
```

### get_conversation

All messages in a conversation, with sender, text, time and attached files. Access: read. REST: `POST /api/v1/dribbble/get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |

Returns the messages of one conversation, oldest first, with the sender, text, time and any attached files. Your agent reads the whole thread before it drafts a reply.

Example response:

```json
{
  "conversation_id": "8841207",
  "with": "Marta Kowal",
  "messages": [
    {
      "from": "Marta Kowal",
      "body": "Hi! We need a redesign of our analytics dashboard.",
      "sent_at": "2026-10-10T08:14:00Z",
      "attachments": []
    }
  ]
}
```

### list_leads

Project and Service Requests you received, with client, date, type and whether you replied. Access: read. REST: `POST /api/v1/dribbble/list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | date | no | Only leads received on or after this date. |
| `unanswered_only` | boolean | no | Skip leads you already replied to. |

Lists the Project and Service Requests you received, newest first, the same requests Pro Analytics counts as Leads. Each item has the client, the date, the request type and whether you have replied. Use unanswered_only to see what still needs an answer.

Example response:

```json
{
  "leads": [
    {
      "lead_id": "ld_30912",
      "client": "Marta Kowal",
      "type": "Project Request",
      "received_at": "2026-10-08T11:02:00Z",
      "replied": false,
      "conversation_id": "8841207"
    }
  ],
  "next_cursor": null
}
```

### list_comments

Comments on one of your shots, with author, text, time and whether you replied. Access: read. REST: `POST /api/v1/dribbble/list_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shot_id` | string | yes | Shot ID from list_shots. |
| `unanswered_only` | boolean | no | Skip comments you already replied to. |

Lists the comments on one of your shots, newest first, with the author, text, time and whether you replied. Set unanswered_only to skip comments you already answered. Pass comment_id to reply_to_comment.

Example response:

```json
{
  "shot_id": "21847531",
  "comments": [
    {
      "comment_id": "c_4471",
      "author": "Jonas Weber",
      "body": "Clean grid. What spacing scale is this?",
      "created_at": "2026-10-09T17:40:00Z",
      "replied": false
    }
  ],
  "next_cursor": null
}
```

### upload_shot

Publish a new shot from an image, with title, description and tags. Access: write, asks the user first. REST: `POST /api/v1/dribbble/upload_shot`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `image_url` | string | yes | PNG, JPG or GIF by URL. |
| `title` | string | yes | Shot title. |
| `description` | string | no | Text shown under the shot. |
| `tags` | string[] | no | Tags that help the shot show up in search. |
| `publish_at` | datetime | no | Schedule it, ISO 8601 with time zone. |

Publishes a new shot on your profile from an image URL, with a title, an optional description and tags. Set publish_at to schedule it. The shot appears under your name and is public once published. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "shot_id": "21901377",
  "status": "published",
  "title": "Fintech dashboard",
  "tags": [
    "ui",
    "fintech",
    "dashboard"
  ],
  "url": "https://dribbble.com/shots/21901377-Fintech-dashboard",
  "published_at": "2026-10-11T10:00:00+02:00"
}
```

### update_shot

Change the title, description or tags of one of your shots. Access: write. REST: `POST /api/v1/dribbble/update_shot`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shot_id` | string | yes | Shot ID from list_shots. |
| `fields` | object | yes | Any of title, description, tags. |

Changes the title, description or tags of one of your own shots. Fields you leave out stay as they are. It sends nothing to anyone and one more call restores the old text, so it runs without asking first.

Example response:

```json
{
  "shot_id": "21847531",
  "status": "updated",
  "title": "Fintech dashboard v2",
  "tags": [
    "ui",
    "fintech",
    "dashboard"
  ]
}
```

### reply_to_message

Send a message as you in an existing conversation. Access: write, asks the user first. REST: `POST /api/v1/dribbble/reply_to_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `body` | string | yes | Message text. |

Sends a message in an existing conversation, under your name. The other person sees it in their Dribbble Messages. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "55120934",
  "conversation_id": "8841207",
  "status": "sent",
  "sent_at": "2026-10-10T14:22:05+02:00"
}
```

### reply_to_comment

Reply as you under a comment on one of your shots. Access: write, asks the user first. REST: `POST /api/v1/dribbble/reply_to_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `comment_id` | string | yes | Comment ID from list_comments. |
| `body` | string | yes | Reply text. |

Posts a reply under one comment on your shot, under your name. The reply is public on the shot. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "c_4480",
  "reply_to": "c_4471",
  "status": "published"
}
```

## How do I connect Dribbble to Claude Code, Codex or Cursor?

Connecting Dribbble takes three steps: request access, sign in to Dribbble once, then add one MCP server or call the REST API with the same key.

### Connect Dribbble to your agent.

1. **Create an account** Sign up and add Dribbble in the console. Your API key is there too.

2. **Sign in to Dribbble once** Open the connect page from the console and sign in to Dribbble the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Dribbble tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through my Dribbble Project Requests and unread messages from this week. Draft a reply or a polite decline for each one I have not answered, and show me every draft before it is sent.
```

### Call Dribbble from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/dribbble/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/dribbble/reply_to_message \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"conversation_id":"8841207","body":"Thanks for reaching out! I can start on the dashboard redesign next week. Could you share the current screens?"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "message_id": "55120934",
  "conversation_id": "8841207",
  "status": "sent",
  "sent_at": "2026-10-10T14:22:05+02:00"
}
```

## Why use Cotlet for Dribbble?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Dribbble yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Dribbble changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Dribbble MCP server on GitHub?

Yes, for reading public data. A few community MCP servers for Dribbble exist on GitHub, usually maintained by one person. The ones that use the official API are read only and cannot reach Messages, leads or Pro Analytics. You install and fix them yourself. Cotlet hosts and maintains a server for you that also covers those parts of your account.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, register an API app, add client ID and secret to each MCP client | Request access, sign in to Dribbble once, add one MCP server or API key |
| What it covers | What API v2 allows: your shots, profile and projects | Also Messages, leads, comments and Pro Analytics |
| When Dribbble changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Dribbble session | OAuth token in a file on your computer | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Dribbble changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Dribbble API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Dribbble API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Dribbble account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Dribbble yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Dribbble tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Dribbble in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Dribbble's terms:** You use your own Dribbble account and stay responsible for following Dribbble's terms. Cotlet is independent and not affiliated with Dribbble. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Dribbble. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Dribbble once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Dribbble session would leave my computer.**

Cotlet keeps your Dribbble session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need a Pro account?**

Only for Pro Analytics. Dribbble lists it in its Pro help collection, so get_pro_analytics needs a Pro account. Shots, comments and Messages tools work in your own account.

**Can it upload a video shot?**

upload_shot takes an image by URL. The official API cannot create video shots ("not yet supported", checked 11 Oct 2026).

**Can my agent post or send messages in Dribbble without asking me?**

No. Every call to upload_shot, reply_to_message or reply_to_comment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_shot runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Dribbble API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/dribbble/{tool} from the HTTP Request node.