What can you do with the Dribbble integration?

LiveContext exposes 18 operations on Dribbble, covering shot, project, job and like. Common uses include portfolio organization, description updates and organization changes.

LiveContext

All integrations

Dribbble integration

Design community platform API for discovering and showcasing creative work. Access shots (design posts), user profiles, projects, and job listings. Perfect for building design inspiration tools, portfolio integrations, and creative asset galleries. Connect with the world's top designers and design teams.

18 toolsOAuthAPI docs

Connect Dribbble How integrations work

Common Dribbble use cases

portfolio organization
description updates
organization changes
work showcase
file cleanup
unlike toggle
project cleanup
error correction
project renaming
portfolio cleanup

What you can do with Dribbble

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Shot, 5 operations

POSTcreate_shot
Uploads a new shot (design post) to Dribbble. Requires upload OAuth scope. User must be player or team member.
DELETEdelete_shot
Permanently deletes a shot from Dribbble. Only the owner can delete and action cannot be undone.
GETget_shot
Retrieves detailed information about a specific shot including high-res images and engagement metrics.
GETlist_user_shots
Lists all shots (design posts) created by the authenticated user with pagination support.
PUTupdate_shot
Updates an existing shot's title, description, tags, or visibility. Only the shot owner can make updates.

Project, 4 operations

POSTcreate_project
Creates a new project to organize related shots together.
DELETEdelete_project
Permanently deletes a project. Returns the deleted project object.
GETlist_projects
Lists all projects created by the authenticated user. Projects group related shots together.
PUTupdate_project
Updates an existing project's name or description.

Job, 3 operations

POSTcreate_job
Posts a job listing to the Dribbble Jobs page. Requires special partnership token.
GETget_job
Retrieves details for a specific job listing by ID.
PUTupdate_job
Updates an existing job listing. link_to_apply and description are required for updates.

Like, 3 operations

POSTlike_shot
Likes a shot on Dribbble. Likes are public and notify the shot owner.
GETlist_user_likes
Lists all shots liked by the authenticated user for building inspiration collections.
DELETEunlike_shot
Removes a like from a shot. Undoes previous like action without notification.

Attachment, 2 operations

POSTcreate_shot_attachment
Uploads a file attachment to a shot. Requires upload scope, shot ownership, and Pro/Team membership.
DELETEdelete_shot_attachment
Deletes an attachment from a shot. Requires upload scope and attachment ownership.

User, 1 operation

GETget_authenticated_user
Retrieves profile information for the currently authenticated user including name, bio, and social stats.

Dribbble API rate limits

60 requests per minute
1,440 requests per day

Rate limits are per authenticated user. 60 requests per minute, 1440 per day. Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. HTTP 429 returned when exceeded.

These are the limits Dribbble documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Dribbble documentation for current values.

Use Dribbble from Claude Code, Cursor or Codex

Connect Dribbble in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dribbble operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dribbble

Create your workspace
Sign up free. Nothing to install.
Connect Dribbble once
Add your Dribbble connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Dribbble integration FAQ

What can you do with the Dribbble integration?: LiveContext exposes 18 operations on Dribbble, covering shot, project, job and like. Common uses include portfolio organization, description updates and organization changes.
What are the Dribbble API rate limits?: Dribbble documents 60 requests per minute and 1,440 requests per day. Rate limits are per authenticated user. 60 requests per minute, 1440 per day. Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. HTTP 429 returned when exceeded. Limits are set by Dribbble and can depend on your plan.