Design & Creative Tools · Penpot + Claude
Penpot MCP with Claude: Faster Design Reviews and Handoffs for Product Teams
The short answer
Claude works with Penpot through the Model Context Protocol, an open standard that lets Claude securely read from and act within the tool. Once connected with an API key, Claude can inspect design files, review comments, manage projects and summarise prototypes using natural language. Access is limited to what the organisation permits.
What is Penpot?
Penpot is an open-source design and prototyping platform built for product teams. It runs in the web browser, so designers, product managers and developers can work on the same user interface files without installing heavy desktop software. Its developer-friendly approach helps teams hand over designs with less back-and-forth. Teams that value open tools and collaborative design often choose Penpot for shared product work.
How Claude connects to Penpot through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool such as Penpot in a secure, structured way, reading information and taking actions only where the organisation has allowed it.
Once connected, Claude can typically read design files, look through comments left by reviewers, check project structures and summarise prototypes. A product manager could ask in plain language for a list of open design questions, and Claude would gather them from the relevant files and present them in a clear summary.
Permissions and approvals keep people in charge. Access is granted through an API key with the scope the organisation chooses, and consequential actions can be set to require human sign-off. Audit logs record what Claude accessed, so teams can review its activity at any time.
What you can automate
Design review summaries
Claude can read through comment threads on a set of screens and produce a short summary of feedback grouped by theme, such as layout, copy or accessibility. Designers spend less time scrolling through long threads and can move straight to the changes that matter most before the next review meeting.
Prototype walkthrough notes
After a prototype is updated, Claude can summarise the key flows and screens so that stakeholders who were not involved in the work understand what has changed. This is useful for product owners and executives who need a quick overview before approving a release.
Project housekeeping
Claude can help review how projects and files are organised, flagging unused files or inconsistent naming so the team keeps its workspace tidy. Design operations leads can use these reports to plan clean-up work during quieter sprints.
Developer handoff preparation
Claude can inspect frames and components and prepare a plain-language brief for developers, listing screens, states and interactions that need building. This reduces the number of clarification messages developers send and helps them start work sooner.
Feedback tracking across teams
Claude can gather open comments from several design files and draft a weekly status note for the product team. Leads gain a consistent view of outstanding design decisions without needing to check each file individually.
An end-to-end workflow: Sprint design review to engineering ticket
TriggerEvery Monday at 9 a.m., or when a designer marks a set of Penpot screens as ready for review.
Claude reads the comments and status of the screens marked for review in Penpot.
Claude groups the feedback into themes and removes duplicate points.
Claude drafts a summary and proposed tasks, and sends them to the design lead for approval.
After approval, Claude creates matching work items in the team's ticketing system, linked to the relevant Penpot files.
Developers receive tickets with clear references to the design, and the design lead tracks progress in one place.
OutcomeDesign feedback reaches engineering in a structured form within hours rather than days. Teams typically report fewer clarification messages and a clearer link between design decisions and delivered work.
How we set it up
Free automation audit
We review how your product and design teams currently use Penpot, review cycles and handoffs, and identify the workflows worth automating first. The audit is free and carries no obligation.
Secure connection
We connect Claude to Penpot using an API key, scoped with least-privilege access so Claude can only reach the projects and files your team approves.
Workflow design
We design the end-to-end workflow across Penpot and your other systems, such as Microsoft 365, your CRM, your ticketing tool or ERP. People approve any consequential actions before they happen.
Testing and launch
We test the workflow against real past design reviews and handoffs, then launch with monitoring and audit logs enabled so you can see exactly what Claude did.
Team training
We train designers, product managers and developers on how to use the new workflow, what Claude can and cannot do, and how to raise issues, so adoption is smooth from day one.
Who benefits
- Product designers
- Spend less time summarising long comment threads and more time improving the interface.
- Product managers
- Get clear, current summaries of prototypes and open design questions without opening every file.
- Front-end and mobile developers
- Receive structured handoff briefs that reduce clarification messages and speed up build work.
- Design operations leads
- Keep projects organised and track feedback across teams from a single, consistent view.
Security and control
- Access is controlled through an API key with the minimum permissions needed for the agreed workflow.
- Claude only reaches the projects and files that your team has explicitly approved.
- Consequential actions, such as creating tickets or changing shared files, can require human approval before they run.
- Audit logs record what Claude accessed and did, so activity can be reviewed at any time.
- API keys are stored securely and can be rotated or revoked at any point by your administrators.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to meet their data protection and procurement requirements. Teams in India must consider the Digital Personal Data Protection Act, 2023, and we design data flows to respect its obligations. Organisations in the UAE and Saudi Arabia must comply with their local data protection laws, and we select a hosting region that suits those requirements. Final compliance depends on each organisation's own legal review.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Penpot MCP server do?
The Penpot MCP server is the bridge that lets AI tools like Claude communicate with Penpot in a structured way. It makes it possible to inspect design files, read comments, manage projects and summarise prototypes through natural language requests. It works within the permissions set by the organisation, so only approved content and actions are available.
Is connecting Penpot to Claude secure?
Security depends on how the connection is set up. We use an API key with least-privilege access, limit Claude to approved projects and files, and require human approval for consequential actions. Audit logs record activity, and keys can be rotated or revoked at any time. Your IT team stays in control throughout.
What can Claude actually do with Penpot?
Once connected, Claude can typically read design files, review comment threads, check project structures and summarise prototypes. It can draft handoff briefs and status notes for your team. Changes to shared work can be set to require approval, so Claude supports your designers rather than replacing their decisions.
How long does setup take?
Timelines vary with the number of projects, the systems involved and the complexity of the workflow. A focused, single-workflow setup often takes a few weeks, including testing and team training. We confirm a realistic timeline during the free automation audit, once we understand your current process.
Which plan or permissions do I need?
You need access to Penpot through an API key, and the key's permissions should match the workflow you want to automate. Requirements can depend on your Penpot setup and your organisation's policies. During the free audit, we check what your team currently has and advise what, if anything, needs to change.