Dribbble
Dribbble is a design community and publishing platform for managing shots, projects, and attachments. Automated mutations must be specifically requested by the user.
Verdict
Common use cases
- Publish design iterations with AI-drafted captions
- Organize recent shots into portfolio projects
- Audit live work and remove outdated shots
- Draft project descriptions from shot metadata
- Check upload eligibility before batch posting
Integration
- Vendor
- Dribbble
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 12
- Composio slug
dribbble
Tools
- Create Project
Create a project for the connected Dribbble user.
- Create Shot
Upload an image to create a public Dribbble shot asynchronously. The connected user must be a player or team and eligible to upload shots. Returns the shot location without polling or claiming processing is complete.
- Delete Projectdestructive
Permanently delete a project belonging to the connected Dribbble user. Returns deletion confirmation and the provider's project fields when supplied.
- Delete Shotdestructive
Permanently delete a shot owned by the connected Dribbble user. This action is irreversible and returns the deleted shot ID as confirmation.
- Delete Shot Attachmentdestructive
Permanently delete an attachment from a shot owned by the connected Dribbble user. This action is irreversible and returns both IDs as confirmation.
- Get Current User
Return the connected Dribbble user's profile, account capabilities, teams, and shot-upload eligibility.
- Get My Shot
Return one shot owned by the connected user, including its media, tags, projects, and attachments. Choose HTML or plain-text description representation.
- List My Projects
Return one page of projects belonging to the connected Dribbble user, with a safe cursor for the next page.
- List My Shots
Return one page of shots owned by the connected Dribbble user, with a safe cursor and selectable HTML or plain-text description representation.
- Update Project
Update the name or description of a project belonging to the connected user.
- Update Shot
Update an owned Dribbble shot's metadata and choose the HTML or plain-text description representation returned in the response.
- Upload Shot Attachment
Upload a file attachment to an owned Dribbble shot asynchronously. This requires a Pro user, team, or team membership. A successful response only confirms acceptance; retrieve the shot later to discover the attachment ID.
Setup
Setup guide
- 11. Inside Switchy, open Settings → Integrations and click Connect next to Dribbble. 2. You'll land on Dribbble's OAuth consent screen; log in with your Dribbble account. 3. Grant read and write access to your shots, projects, and profile — the MCP needs both to create and delete content. 4. Switchy confirms the connection and shows your Dribbble username. 5. Open any Project, type '@Dribbble get my profile' and send — if you see your account details and upload eligibility, the connection works. 6. To upload a shot, attach an image in the chat and write '@Dribbble create a shot with this image, title: [your title], description: [your description]' — the MCP returns the shot URL once processing finishes.
What teammates see: by default, memories from Dribbble are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Upload Today's Work
@Dribbble create a shot with the attached image. Write a concise title and a two-sentence description that highlights the design challenge and solution.
Organize Into Projects
@Dribbble list my recent shots, then create a project called 'Q1 Brand Work' and suggest which shots belong in it based on style and subject.
Audit Portfolio
@Dribbble get my profile and list my shots. Flag any that are more than two years old or don't match my current design direction.
Draft Project Description
@Dribbble get the shots in my 'Mobile Redesign' project and write a 100-word project description that ties them together into a case study narrative.
Clean Up Old Shots
@Dribbble list my shots and delete any that include the old logo or color palette we retired last quarter.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@dribbble list my projects and show me which ones have the most shots so I can decide what to feature on my portfolio site
Retrieved 8 projects from your Dribbble account. Your 'Mobile UI Explorations' project leads with 23 shots, followed by 'Brand Identity Work' with 17 shots and 'Icon Systems' with 12 shots. The remaining 5 projects contain between 3-8 shots each. All projects are currently public. This data reflects your account state as of this query; shot counts update when you publish or delete work.
This example demonstrates read-only project enumeration, which requires OAuth2 consent but poses no side-effect risk. Useful for portfolio curation decisions or understanding your own content distribution. The MCP returns paginated results; accounts with 50+ projects will need cursor-based navigation to see everything.
@dribbble create a new shot from the file 'dashboard-redesign-v3.png' in this conversation, title it 'SaaS Dashboard Refresh', and tag it with 'UI', 'dashboard', 'SaaS'
Shot created successfully and uploaded to your Dribbble profile. The shot 'SaaS Dashboard Refresh' is now live at dribbble.com/shots/[id] with tags 'UI', 'dashboard', and 'SaaS' applied. Upload completed asynchronously; the image is publicly visible immediately. Note that this action consumed one shot upload from your account quota (players and teams have monthly limits based on membership tier).
This write operation requires the connected user to have Player or Team status on Dribbble—Pro accounts without upload eligibility will fail. The MCP does not poll for processing completion; shots appear live within seconds but thumbnail generation may lag. Be mindful of your monthly upload quota, which varies by account type and is not surfaced in the response.
@dribbble get my last 10 shots and write a short bio paragraph summarizing my design style based on the titles, tags, and descriptions
Analyzed your 10 most recent shots: 'Fintech Onboarding Flow', 'Minimalist Icon Set', 'Dark Mode Toggle Animation', and 7 others. Your work centers on clean, functional interfaces with a strong emphasis on micro-interactions and accessibility. Recurring tags include 'minimalism', 'animation', 'mobile-first', and 'design systems'. Your descriptions frequently reference user research and iterative testing, suggesting a UX-driven approach. This synthesis is based on metadata only; the MCP does not analyze image content or color palettes.
This synthesis example pairs the MCP's shot-listing capability with the AI's reasoning to generate portfolio copy. The output quality depends on how thoroughly you've tagged and described your work—sparse metadata yields generic summaries. The MCP retrieves shots in reverse-chronological order; specify a project filter if you want style analysis scoped to a particular body of work.
Use-case deep-dives
When Dribbble MCP makes sense for component libraries
A 6-person product team maintaining a design system in Figma wants to auto-publish component screenshots to Dribbble as they ship. The Dribbble MCP is the right call if you already use Dribbble as your public portfolio and want to skip manual uploads. The Create Shot tool pushes images directly; the Create Project tool organizes them into collections. The catch: this only works if the connected account is a Dribbble Player or Team—free accounts can't upload shots. If your team doesn't already pay for Dribbble or doesn't use it as a portfolio, the MCP adds no value over a manual upload. But if you're shipping visual work weekly and Dribbble is your showcase, the automation saves 10 minutes per component release.
Why solo designers hit the OAuth ceiling fast
A freelance designer working with 3-4 clients at once wants to use Switchy to draft concepts and push them to Dribbble for client review. The Dribbble MCP supports this—barely. The OAuth2 flow ties the connection to one Dribbble account, so you can't switch between client portfolios without re-authenticating. The Get Current User and List My Projects tools help you confirm which account is active, but if you manage multiple Dribbble profiles (one per client or one personal), you'll spend more time re-authing than the MCP saves. This scenario works cleanly only if you publish everything to a single Dribbble account and use projects to separate clients. If you need multi-account flexibility, skip the MCP and upload manually.
When bulk deletion justifies the 12-tool overhead
A 10-person agency wants to archive old Dribbble shots and projects from 2019-2021 that no longer reflect their current style. The Dribbble MCP's Delete Shot and Delete Project tools let you script the cleanup instead of clicking through the web UI 200 times. The List My Projects tool paginates through your portfolio; you filter by date or tag in your script, then call the delete tools in a loop. The trade-off: OAuth2 setup and the 12-tool footprint are overkill if you're only deleting 10-20 items—just use the Dribbble web UI. But if you're pruning 100+ shots or need to delete attachments (Delete Shot Attachment), the MCP pays off in 30 minutes of saved clicking. This is a one-time job, not a recurring workflow.
Frequently asked
What does the Dribbble MCP let me do in Switchy?
It lets your AI agents create, read, and delete shots and projects on your Dribbble account. Agents can upload images as shots, organize them into projects, manage attachments, and fetch your profile details. It's built for teams that want to automate portfolio updates or batch-publish design work without opening the Dribbble web app.
Do I need to be a Dribbble Pro or Team account to connect this?
You need to be a Dribbble Player or Team member to upload shots via the MCP. Regular users can still connect and read their profile or projects, but shot creation will fail. The OAuth flow will tell you if your account lacks upload eligibility before you try to publish anything.
Can the MCP edit existing shots or just create new ones?
It can only create new shots and delete shots you own. There's no update or edit tool—if you need to change a shot's title, description, or tags, you'll have to delete and re-upload it or use Dribbble's web interface. The MCP also can't manage comments, likes, or views.
Why use this instead of uploading shots manually on Dribbble?
If you're publishing dozens of design variants, exporting frames from Figma, or syncing work from another tool, the MCP saves you from opening Dribbble repeatedly. An agent can batch-upload shots, tag them consistently, and sort them into projects in one go. For one-off uploads, the web app is faster.
Who on my team should connect their Dribbble account?
Whoever owns the Dribbble profile where shots should appear. If you're a team account, connect the team owner or a member with upload permissions. Switchy doesn't share one connection across users—each person who wants to publish shots needs to OAuth their own Dribbble account.