Penpot
Open-source design and prototyping platform for collaborative design workflows
Verdict
Common use cases
- Drop comment threads on mockups from standup
- Spin up projects for each sprint automatically
- Track design file changes via webhook
- Onboard contractors by requesting team access
- Audit active API tokens across the org
Integration
- Vendor
- Penpot
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 50
- Composio slug
penpot
Tools
- Create Access Token
Tool to create a personal access token for API authentication in Penpot. Use when you need to generate a new token for authenticating API requests. The token will only be shown once during creation, so it should be stored securely.
- Create Comment Thread
Tool to create a new comment thread on a Penpot file at a specific position. Use when you need to add collaborative feedback or discussion points on design elements within a Penpot project.
- Create File
Tool to create a new design file in a Penpot project. Use when you need to create a new file for design work within a specific project.
- Create Project
Tool to create a new project within a team in Penpot. Use when you need to organize design files into a new project space.
- Create Team
Tool to create a new team in Penpot. Use when you need to set up a new team for organizing projects and collaborating with team members.
- Create Team Access Request
Tool to request an invitation to join a Penpot team. Use when a user needs to request access to a team for collaboration.
- Create Webhook
Create a webhook for a team to receive event notifications. Use when you need to register a new webhook endpoint that will be notified of events happening in a Penpot team.
- Delete Access Tokendestructive
Tool to delete a personal access token from Penpot. Use when you need to revoke or remove an existing access token by its UUID.
- Delete Commentdestructive
Tool to delete a comment from a Penpot design file. Use when you need to permanently remove a specific comment from a design discussion.
- Delete File Snapshotdestructive
Tool to delete a file snapshot in Penpot. Use when you need to remove a previously created snapshot from a file.
- Delete Projectdestructive
Tool to delete a project from Penpot. Use when you need to permanently remove a project and all its contents.
- Delete Teamdestructive
Tool to delete a team from Penpot. Use when you need to permanently remove a team. This operation is irreversible.
- Delete Team Invitationdestructive
Tool to delete a pending team invitation in Penpot. Use when you need to cancel an invitation that hasn't been accepted yet.
- Delete Team Memberdestructive
Tool to remove a member from a team in Penpot. Use when you need to revoke a user's access to a team.
- Delete Webhookdestructive
Tool to delete a webhook by its UUID. Use when you need to remove a webhook from Penpot.
- Duplicate File
Tool to duplicate a single file within the same team in Penpot. Use when you need to create a copy of an existing design file.
- Duplicate Project
Tool to duplicate an entire Penpot project with all its files. Use when you need to create a copy of an existing project.
- Get Access Tokens
Tool to list all personal access tokens for the authenticated user. Use when you need to view, audit, or manage existing access tokens.
- Get All Projects
Tool to retrieve all projects across all teams in Penpot. Use when you need a complete list of projects regardless of team membership.
- Get Builtin Templates
Tool to get the list of builtin templates available in Penpot. Use when you need to see which templates are available for creating new projects.
- Get Comments
Tool to retrieve all comments in a comment thread. Use when you need to fetch all comments from a specific thread.
- Get Comment Thread
Tool to retrieve a specific comment thread from a Penpot file. Use when you need to fetch details about a comment thread including its comments, participants, and metadata.
- Get Comment Threads
Tool to retrieve all comment threads for a Penpot file. Use when you need to fetch comments and discussions associated with a specific file.
- Get File
Tool to retrieve a Penpot file by its ID. Returns file details including metadata, structure, and permissions. Use when you need to access file information or check file properties.
- Get File Info
Tool to retrieve basic information about a Penpot file by its ID. Use when you need to get file metadata such as name, project, creation date, modification date, version, and sharing status.
- Get File Libraries
Tool to retrieve libraries linked to a Penpot file. Use when you need to get all library references associated with a specific file by its UUID.
- Get File Object Thumbnails
Tool to retrieve thumbnails for objects in a Penpot file. Use when you need to get thumbnail URLs for file objects.
- Get File Snapshots
Retrieves all snapshots for a specific Penpot file. Use this action to list all saved versions (snapshots) of a file, which allows viewing version history and understanding how the file has evolved over time. Snapshots capture the state of
- Get File Summary
Tool to retrieve a summary of file contents and statistics from Penpot. Use when you need high-level information about a file including page count, components, graphics, and other metadata without fetching the entire file content.
- Get Font Variants
Tool to retrieve font variants for a team, file, project, or share in Penpot. Use when you need to get a list of available font variants. Provide at least one of team_id, file_id, project_id, or share_id to scope the query.
- Get Library File References
Tool to get files that reference a shared library. Use when you need to find which files are using a specific library file in Penpot.
- Get Library Usage
Tool to get usage statistics for a library. Returns the number of files that use the specified library. Use when you need to understand how widely a library is being used across projects.
- Get Owned Teams
Tool to list teams owned by the current user. Use when you need to retrieve teams that the authenticated user owns in Penpot.
- Get Page
Tool to retrieve page data from a Penpot file. Use when you need to get page content including objects and metadata for rendering or export purposes. If no page ID is specified, returns the first page. Can filter to a specific object and it
- Get Profiles for File Comments
Tool to retrieve profiles of users who have commented on a Penpot file. Use when you need to get information about comment participants for collaboration or user management purposes.
- Get Project
Tool to retrieve detailed information about a specific Penpot project by its ID. Use when you need to get project details such as name, team ownership, and timestamps.
- Get Project Files
Tool to retrieve all files in a Penpot project. Use when you need to list all files for a specific project by its UUID.
- Get SSO Provider
Tool to retrieve SSO provider information for an email address. Use when you need to determine which SSO provider is configured for a specific email domain.
- Get Subscription Usage
Tool to get subscription usage information for the current user. Returns details about seats and storage usage. Use when you need to check subscription limits or current usage statistics.
- Get Team
Tool to retrieve team details by ID. Use when you need to fetch information about a specific team in Penpot.
- Get Team Deleted Files
Tool to retrieve deleted files from a team's trash in Penpot. Use when you need to view files that have been deleted from a specific team and are in the trash.
- Get Team Info
Tool to retrieve detailed information about a specific Penpot team by its ID. Use when you need to get team details such as name, creation date, and permissions.
- Get Team Invitations
Tool to list pending invitations for a team in Penpot. Use when you need to retrieve all pending team invitations that haven't been accepted yet.
- Get Team Members
Tool to list all members of a team in Penpot. Use when you need to retrieve team membership information and member details.
- Get Teams
Tool to list all teams the authenticated user is a member of. Use when you need to retrieve teams where the user has membership in Penpot.
- Get Team Shared Files
Tool to retrieve shared library files for a Penpot team. Use when you need to list all shared library files for a specific team by its UUID.
- Get Team Stats
Tool to retrieve statistics for a specific Penpot team by its ID. Use when you need to get team metrics such as project count, file count, and member count.
- Get Team Users
Tool to retrieve users in a team by team ID or file ID. Use when you need to list team members associated with a specific team or file.
- Get Unread Comment Threads
Tool to retrieve comment threads with unread comments for a specific team. Use when you need to check for new comments or discussions requiring attention.
- Permanently Delete Team Filesdestructive
Tool to permanently delete specified files from a Penpot team. Use when you need to immediately and irreversibly remove files from a team. The team ID is used to filter files and verify write permissions.
Setup
Setup guide
- 11. Open your Penpot workspace and navigate to your profile settings to generate a new API access token. 2. Copy the token immediately — Penpot shows it only once. 3. In Switchy, click Integrations in the left sidebar, find Penpot, and select Connect. 4. Paste your API key into the prompt and click Authorize. 5. Switchy confirms the connection and lists the teams and projects it can access. 6. Open any Space, type '@Penpot create a project called Q1 Launch in the Marketing team', and send. 7. The MCP responds with the new project ID and a link to view it in Penpot. 8. To verify webhooks work, ask '@Penpot create a webhook for the Design team pointing to https://example.com/hook' and check your endpoint receives a test ping.
What teammates see: by default, memories from Penpot are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
New Sprint Project
@Penpot create a new project called 'Sprint 12 - Checkout Redesign' in the Product teamOpen in a Space →
Add Feedback Thread
@Penpot create a comment thread on file abc123 at position x:200 y:300 saying 'Should this button be primary or secondary color?'Open in a Space →
Webhook for Deploys
@Penpot create a webhook for the Engineering team that posts to https://ci.example.com/design-updatesOpen in a Space →
Request Team Access
@Penpot create a team access request for user jane@example.com to join the Marketing teamOpen in a Space →
Revoke Old Token
@Penpot delete the access token with UUID def456-789ghi-012jklOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Penpot show me all comment threads on the mobile-app-redesign file and summarize the main design feedback themes
I found 12 comment threads on the mobile-app-redesign file. The feedback clusters into three themes: (1) Navigation concerns — 5 threads discuss bottom-nav accessibility and tap-target sizing. (2) Color contrast — 4 threads flag WCAG AA failures on secondary buttons. (3) Onboarding flow — 3 threads suggest simplifying the signup wizard from 4 steps to 2. Most threads are unresolved and assigned to the design-review label.
This example shows the MCP's ability to fetch comment data and pair it with AI synthesis. Requires read access to the specified file. If your Penpot instance has hundreds of threads, response time may increase — consider filtering by date or label in the prompt.
@Penpot create a new project called 'Q2 Marketing Assets' in the Brand team and add a file named 'social-templates'
Project created: 'Q2 Marketing Assets' is now live in the Brand team workspace. I've added a blank file called 'social-templates' inside it. The project URL is https://design.penpot.app/#/workspace/abc123/project/def456. Team members with Brand access can now open the file in Penpot and start designing.
Demonstrates the MCP's project and file creation tools. This writes to your Penpot workspace, so the user must have team-admin or project-creation permissions. The new file starts empty — designers will need to open Penpot to add frames and components.
@Penpot set up a webhook pointing to https://hooks.example.com/penpot-events so we get notified when files are updated in the Design System team
Webhook registered successfully. Endpoint: https://hooks.example.com/penpot-events. Team: Design System. Event types: file:created, file:updated, file:deleted. Penpot will POST JSON payloads to this URL whenever a file changes. Webhook ID: wh_789xyz — save this if you need to delete or update the webhook later.
Showcases the MCP's webhook tool for event-driven workflows. Requires team-admin permissions and a publicly accessible HTTPS endpoint. Your server must respond with 2xx status codes or Penpot will disable the webhook after repeated failures.
Use-case deep-dives
When this MCP saves your dev team from pixel-pushing
A 5-person product team ships features every two weeks. Before handoff, the PM and lead dev walk through Penpot mockups in a shared Switchy session, dropping comment threads on spacing issues and missing states. The MCP creates threads at exact coordinates, tags the designer, and logs the feedback in Linear via webhook—all without leaving the AI workspace. This works when your design files live in Penpot and you need structured feedback loops. If your team uses Figma or Sketch, this MCP won't help. The 50-tool scope means you can also script project setup and token rotation, but the real win is eliminating Slack screenshot tennis during QA. Use this when design review happens in standup and you want the AI to write the tickets.
How agencies use this MCP to spin up client workspaces
A 12-person design agency onboards 3-4 new clients per month. Each client needs a Penpot team, starter projects, and webhook integrations to their Slack. The ops lead runs a Switchy prompt that calls the MCP to create the team, scaffold 3 project templates, and register webhooks for file updates. This takes 90 seconds instead of 20 minutes of clicking. The API key auth means one token covers all client setups, but you'll need to rotate it quarterly for security. This scenario breaks down if your agency uses multiple design tools—Penpot's open-source model attracts shops that want full control, but mixed toolchains need a different play. Book this MCP when client setup is repetitive and you bill by the hour.
When distributed maintainers need design context fast
A 7-person open-source project has contributors across 4 time zones. The design lead posts mockups in Penpot; maintainers review async and need to surface questions without scheduling calls. In Switchy, a maintainer asks the AI to pull the latest file, scan for unresolved comment threads, and summarize design decisions in the project README. The MCP reads threads, creates new ones for edge cases, and updates project metadata. This works because Penpot's API exposes full comment history and the MCP's 50 tools cover both read and write operations. If your project has under 10 active contributors or ships designs once a quarter, manual review is faster. Use this when design velocity matters and your team already lives in Penpot for version control.
Frequently asked
What does the Penpot MCP let me do in Switchy?
It connects Switchy to your Penpot design workspace so AI can create projects, add files, post comment threads, and manage team access—all without leaving the chat. You can automate design file setup, pull feedback into conversations, or let AI draft new boards based on your brief. It's useful when you want design ops to happen alongside product discussions in one place.
Do I need admin rights in Penpot to connect this MCP?
You need permission to create a personal access token in your Penpot account, which typically requires member-level access or higher. The token you generate controls what the MCP can do—if your Penpot role can't create projects or teams, the MCP won't be able to either. Admin rights aren't mandatory, but they unlock the full tool set.
Can the Penpot MCP edit existing design files or just create new ones?
It can create new files and projects, add comment threads to existing files, and manage webhooks or team invites. It doesn't directly edit shapes, layers, or artboards inside a file—that still happens in Penpot's editor. Think of it as design ops automation, not a replacement for the design canvas itself.
Why use this instead of just opening Penpot in a browser tab?
Use the MCP when you want AI to handle repetitive setup—spinning up projects for new clients, posting feedback comments in bulk, or wiring webhooks to your build pipeline. If you're designing pixel-by-pixel, stay in Penpot. If you're coordinating ten design files across three teams while chatting with stakeholders, let Switchy's AI do the legwork.
Who on my team should connect the Penpot MCP?
Whoever manages your Penpot workspace or needs to automate design file workflows. Design leads, product ops, or dev leads are common choices. The person connecting it should trust that AI will act with their Penpot permissions—so don't hand the token to someone who shouldn't be creating teams or posting comments on your behalf.