| name | penpot-mcp-connector |
| description | MCP connector for Penpot design platform – enables AI-powered UI design, component management, and prototyping through Claude |
| license | MPL |
| tags | ["creative","design","mcp","penpot","ui"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Penpot MCP Connector
Overview
This skill enables Claude to interact with Penpot through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Penpot's REST API, allowing natural language control of Penpot operations, intelligent automation, and AI-powered assistance for Penpot workflows.
When to Use This Skill
- Component and frame creation via natural language
- Design system and style guide generation
- Prototype flow and interaction creation
- SVG import and manipulation
- Team library management and sharing
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Penpot │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Penpot operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/rpc/command/get-projects, /api/rpc/command/get-file, /api/rpc/command/update-file, /api/rpc/command/get-teams
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "penpot-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Penpot resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/rpc/command/get-projects`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
};
}
);
server.tool(
"create_resource",
"Create a new resource in Penpot",
{
name: z.string().describe("Resource name"),
config: z.object({}).passthrough().optional().describe("Resource configuration"),
},
async ({ name, config }) => {
const response = await fetch(`${BASE_URL}/api/rpc/command/get-projects`, {
method: "POST",
headers: {
"Authorization": `Bearer ${API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ name, ...config }),
});
const data = await response.json();
return {
content: [{ type: "text", text: `Created: ${JSON.stringify(data)}` }],
};
}
);
server.tool(
"analyze",
"AI-powered analysis of Penpot data",
{
type: z.string().describe("Analysis type"),
timeframe: z.string().optional().describe("Time range for analysis"),
},
async ({ type, timeframe }) => {
const response = await fetch(`${BASE_URL}/api/rpc/command/get-projects`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
};
}
);
const transport = new StdioServerTransport();
await server.connect(transport);
Claude Desktop Configuration
{
"mcpServers": {
"penpot-mcp-connector": {
"command": "node",
"args": ["path/to/penpot-mcp-connector/index.js"],
"env": {
"PENPOT_API_KEY": "your-api-key",
"PENPOT_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Penpot API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Penpot API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a design system with button, input, and card components in primary brand colors"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.