How to connect Penpot to OpenClaw
Connect Penpot to OpenClaw with ClawLink: paste your Penpot key once and 90 tools work from chat. No MCP server to run, nothing stored on your machine.
PenpotAPI KEYMCPOpen-source design and prototyping platform for collaborative design workflows.. Once connected, OpenClaw can read and act on Penpot from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Penpot access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Penpot setup: install one ClawHub skill, connect Penpot in the browser, and OpenClaw can call real Penpot actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Penpot skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Penpot" (hith3sh/penpot-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/penpot-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Penpot.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Penpot
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Penpot?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Penpot in the ClawLink dashboard — paste your Penpot API key once.
Verify the connection by asking OpenClaw:
Create it in Penpot for me, then confirm the important fields before you finish.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Penpot is connected in the dashboard, that agent calls the same 90 Penpot tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Penpot MCP for OpenClaw
Looking for a Penpot MCP server for OpenClaw? ClawLink connects Penpot to OpenClaw and exposes 90 Penpot tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Penpot integration works the same way.
What the OpenClaw Penpot integration can do
90 Penpot tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 90.
30 of 90 Penpot tools for OpenClaw
| Tool | What it does |
|---|---|
Create access token penpot_create_access_token | Create a personal access token for API authentication in Penpot |
Create comment thread penpot_create_comment_thread | Create a new comment thread on a Penpot file at a specific position |
Create file penpot_create_file | Create a new design file in a Penpot project |
Create project penpot_create_project | Create a new project within a team in Penpot |
Get access tokens penpot_get_access_tokens | List all personal access tokens for the authenticated user |
Get all projects penpot_get_all_projects | Retrieve all projects across all teams in Penpot |
Get builtin templates penpot_get_builtin_templates | Get the list of builtin templates available in Penpot |
Get comment thread penpot_get_comment_thread | Retrieve a specific comment thread from a Penpot file |
Get comment threads penpot_get_comment_threads | Retrieve all comment threads for a Penpot file |
Get comments penpot_get_comments | Retrieve all comments in a comment thread |
Get file penpot_get_file | Retrieve a Penpot file by its ID |
Get file info penpot_get_file_info | Retrieve basic information about a Penpot file by its ID |
Get file libraries penpot_get_file_libraries | Retrieve libraries linked to a Penpot file |
Get file object thumbnails penpot_get_file_object_thumbnails | Retrieve thumbnails for objects in a Penpot file |
Get file snapshots penpot_get_file_snapshots | Retrieves all snapshots for a specific Penpot file |
Get file summary penpot_get_file_summary | Retrieve a summary of file contents and statistics from Penpot |
Get font variants penpot_get_font_variants | Retrieve font variants for a team, file, project, or share in Penpot |
Get library file references penpot_get_library_file_references | Get files that reference a shared library |
Get library usage penpot_get_library_usage | Get usage statistics for a library |
Get owned teams penpot_get_owned_teams | List teams owned by the current user |
Get page penpot_get_page | Retrieve page data from a Penpot file |
Get profiles for file comments penpot_get_profiles_for_file_comments | Retrieve profiles of users who have commented on a Penpot file |
Get project penpot_get_project | Retrieve detailed information about a specific Penpot project by its ID |
Get project files penpot_get_project_files | Retrieve all files in a Penpot project |
Get sso provider penpot_get_sso_provider | Retrieve SSO provider information for an email address |
Get subscription usage penpot_get_subscription_usage | Get subscription usage information for the current user |
Get team penpot_get_team | Retrieve team details by ID |
Get team deleted files penpot_get_team_deleted_files | Retrieve deleted files from a team's trash in Penpot |
Get team info penpot_get_team_info | Retrieve detailed information about a specific Penpot team by its ID |
Get team invitations penpot_get_team_invitations | List pending invitations for a team in Penpot |
Try it: find the Penpot tool you need
Browse the 30 Penpot tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Penpot for me, then confirm the important fields before you finish.
Create it in Penpot for me, then confirm the important fields before you finish.
Create it in Penpot for me, then confirm the important fields before you finish.
Create it in Penpot for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Penpot working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Penpot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Penpot account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Penpot. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Penpot actions to the runtime in a format your agent can reliably use. | 90 tools for Penpot are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Penpot to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Penpot in the browser, and the 90 tools above work from chat. There is no SDK and no config file, and the Penpot key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Penpot skill but can't call the tools
The ClawHub skill teaches OpenClaw about Penpot, but the calls run through the ClawLink plugin and your connected account. Make sure Penpot is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Penpot from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Penpot tools
Penpot tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Penpot call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Penpot returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Penpot has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Penpot integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Penpot: link your Penpot account once in the browser and OpenClaw can call the Penpot API through 90 ready-made tools — no custom code or token handling.
How do I add Penpot to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Penpot skill from ClawHub, then you click Connect in the dashboard to authorize Penpot. OpenClaw calls the tools from the next message — no config files, and the Penpot key you paste is stored server-side instead of in your environment.
How long does it take to connect Penpot to OpenClaw?
About two minutes. Sign in, click Connect next to Penpot in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Penpot up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Penpot working from chat.
OpenClaw installed the Penpot skill but can't call the tools
The ClawHub skill teaches OpenClaw about Penpot, but the calls run through the ClawLink plugin and your connected account. Make sure Penpot is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
