Penpot MCP Server 🖥️

Created By
cale0ba year ago
Penpot MCP connects design workflows with AI, enhancing creativity and efficiency. This server leverages Model Context Protocol to integrate Claude AI and other LLMs into your Penpot projects. 🐙💻
Overview

what is Penpot MCP?

Penpot MCP is a server that connects design workflows with AI, enhancing creativity and efficiency by integrating Claude AI and other LLMs into Penpot projects.

how to use Penpot MCP?

To use Penpot MCP, clone the repository, install the required dependencies, and run the server. Access it via your web browser at http://localhost:8000.

key features of Penpot MCP?

  • AI Integration for enhanced design processes
  • Cursor Management for improved user interaction
  • Open Source for community contributions
  • Prototyping Tools for easy management of prototypes
  • API Support for integration with other applications

use cases of Penpot MCP?

  1. Streamlining design workflows with AI assistance
  2. Creating and managing prototypes efficiently
  3. Integrating with other applications through API

FAQ from Penpot MCP?

  • Is Penpot MCP free to use?

Yes! Penpot MCP is fully open-source and free to use.

  • How can I contribute to Penpot MCP?

You can contribute by forking the repository, making changes, and submitting a pull request.

  • What technologies does Penpot MCP use?

Penpot MCP is built using Python and leverages AI and LLM technologies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cale0b
Star
1
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago