# How to connect Penpot to Hermes Agent (paste one key, 90 tools) > Connect Penpot to Hermes with ClawLink: paste your Penpot key once and 90 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/penpot Most guides for giving Hermes Agent Penpot access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Penpot setup: pair once in the browser and your always-on Hermes agent can act on Penpot for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to Penpot. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Penpot** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect penpot # connect Penpot (browser OAuth) npx -y @useclawlink/cli actions penpot # list available actions npx -y @useclawlink/cli run penpot --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Penpot in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Penpot API key once. Verify the connection by asking Hermes: > Create it in Penpot for me, then confirm the important fields before you finish. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Penpot MCP for Hermes Looking for a Penpot MCP server for Hermes Agent? ClawLink connects Penpot to Hermes Agent and exposes 90 Penpot tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Penpot integration](https://claw-link.dev/openclaw/penpot) works the same way. ## What the Hermes Agent Penpot integration can do 90 Penpot tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Create Access Token** > Create it in Penpot for me, then confirm the important fields before you finish. **Create Comment Thread** > Create it in Penpot for me, then confirm the important fields before you finish. **Create File** > Create it in Penpot for me, then confirm the important fields before you finish. **Create Project** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Penpot Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Penpot integration? Yes. ClawLink is the fastest way to connect Hermes to Penpot: link your Penpot account once in the browser and Hermes Agent can call the Penpot API through 90 ready-made tools — no custom code or token handling. ### How do I connect Penpot to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Penpot in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Penpot in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Penpot working from chat. ### Hermes paired but still can't use Penpot Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Hermes Cloudinary integration](https://claw-link.dev/hermes/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates - [Figma tools](https://claw-link.dev/hermes/figma) — Design files, prototypes, comments, and developer resources