# How to connect DeployHQ to Hermes Agent (paste one key, 60 tools) > Connect DeployHQ to Hermes with ClawLink: paste your DeployHQ key once and 60 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/deployhq Most guides for giving Hermes Agent DeployHQ 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 DeployHQ setup: pair once in the browser and your always-on Hermes agent can act on DeployHQ for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to DeployHQ. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect DeployHQ** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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. **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 deployhq # connect DeployHQ (browser OAuth) npx -y @useclawlink/cli actions deployhq # list available actions npx -y @useclawlink/cli run deployhq --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 DeployHQ in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your DeployHQ account details once. Verify the connection by asking Hermes: > Pull the relevant data from DeployHQ, summarize it in plain English, and point out anything that needs attention. ### 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 DeployHQ is connected in the dashboard, that agent calls the same 60 DeployHQ 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). ## DeployHQ MCP for Hermes Looking for a DeployHQ MCP server for Hermes Agent? ClawLink connects DeployHQ to Hermes Agent and exposes 60 DeployHQ 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 DeployHQ integration](https://claw-link.dev/openclaw/deployhq) works the same way. ## What the Hermes Agent DeployHQ integration can do 60 DeployHQ 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 60. ### 30 of 60 DeployHQ tools for Hermes | Tool | What it does | |---|---| | **Get projects** `deployhq_get_projects` | Retrieve all projects from DeployHQ account | | **Get projects project** `deployhq_get_projects_project` | View an existing project in DeployHQ | | **Get projects project build known hosts** `deployhq_get_projects_project_build_known_hosts` | List all known hosts within a project using DeployHQ API | | **Get projects project commands** `deployhq_get_projects_project_commands` | Retrieve all SSH commands configured for a project | | **Get projects project config files** `deployhq_get_projects_project_config_files` | Retrieve a list of all config files in a DeployHQ project | | **Get projects project deployments** `deployhq_get_projects_project_deployments` | Retrieve a paginated list of all deployments in a project | | **Get projects project excluded files** `deployhq_get_projects_project_excluded_files` | List all excluded files within a project template | | **Get projects project ID config files ID** `deployhq_get_projects_project_id_config_files_id` | View a specific config file in a DeployHQ project | | **Get projects project ID excluded files ID** `deployhq_get_projects_project_id_excluded_files_id` | View a specific excluded file in a DeployHQ project | | **Get projects project ID server groups ID** `deployhq_get_projects_project_id_server_groups_id` | View a specific server group in a DeployHQ project | | **Get projects project repository** `deployhq_get_projects_project_repository` | View repository details for a specific project in DeployHQ | | **Get projects project repository branches** `deployhq_get_projects_project_repository_branches` | View all available branches in the connected repository for a project | | **Get projects project repository commit info** `deployhq_get_projects_project_repository_commit_info` | View detailed information about a specific revision in a project's connected repository | | **Get projects project repository latest revision** `deployhq_get_projects_project_repository_latest_revision` | View the latest remote revision of your repository | | **Get projects project repository recent commits** `deployhq_get_projects_project_repository_recent_commits` | View up to 15 most recent revisions and up to 15 most recent tags in a specific branch | | **Get projects project scheduled deployments** `deployhq_get_projects_project_scheduled_deployments` | Retrieve all upcoming scheduled deployments for a project | | **Get projects project server groups** `deployhq_get_projects_project_server_groups` | Retrieve all server groups configured for a project | | **Get projects project servers** `deployhq_get_projects_project_servers` | Retrieve all servers configured for a project | | **Get templates** `deployhq_get_templates` | Retrieves all deployment templates from the DeployHQ account | | **Get templates ID public ID** `deployhq_get_templates_id_public_id` | Retrieves detailed configuration for a specific public framework template from DeployHQ's | | **Get templates public templates** `deployhq_get_templates_public_templates` | Retrieve publicly available deployment templates from DeployHQ | | **Post projects ID AI deployment overview** `deployhq_post_projects_id_ai_deployment_overview` | Generate an AI-powered deployment overview for a revision range | | **Patch projects ID** `deployhq_patch_projects_id` | Update project settings in DeployHQ | | **Patch projects project ID build cache files ID** `deployhq_patch_projects_project_id_build_cache_files_id` | Update an existing build cache file in a project | | **Patch projects project ID build commands ID** `deployhq_patch_projects_project_id_build_commands_id` | Update an existing build command in a project | | **Patch projects project ID build languages ID** `deployhq_patch_projects_project_id_build_languages_id` | Updates the version of a programming language in a project's build environment configuration | | **Patch projects project ID commands ID** `deployhq_patch_projects_project_id_commands_id` | Update an existing SSH command in a project | | **Patch projects project ID config files ID** `deployhq_patch_projects_project_id_config_files_id` | Update an existing config file in a DeployHQ project | | **Patch projects project ID excluded files ID** `deployhq_patch_projects_project_id_excluded_files_id` | Update an existing excluded file rule in a project | | **Patch projects project ID repository** `deployhq_patch_projects_project_id_repository` | Update repository configuration for a project in DeployHQ | ## Example prompts **Get Projects** > Pull the relevant data from DeployHQ, summarize it in plain English, and point out anything that needs attention. **Get Projects Project** > Pull the relevant data from DeployHQ, summarize it in plain English, and point out anything that needs attention. **Get Projects Project Build Known Hosts** > Pull the relevant data from DeployHQ, summarize it in plain English, and point out anything that needs attention. **Get Projects Project Commands** > Pull the relevant data from DeployHQ, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 DeployHQ working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right DeployHQ credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link DeployHQ without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for DeployHQ. | 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 DeployHQ actions to the runtime in a format your agent can reliably use. | 60 tools for DeployHQ are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DeployHQ 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 DeployHQ in the browser, and the 60 tools above work from chat. There is no SDK and no config file, and the DeployHQ 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 DeployHQ 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 DeployHQ 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 DeployHQ tools DeployHQ 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 DeployHQ 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. ### DeployHQ 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for DeployHQ. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a Hermes Agent DeployHQ integration? Yes. ClawLink is the fastest way to connect Hermes to DeployHQ: link your DeployHQ account once in the browser and Hermes Agent can call the DeployHQ API through 60 ready-made tools — no custom code or token handling. ### How do I connect DeployHQ 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 DeployHQ in the dashboard and Hermes can use it from the next message — no config files, and the DeployHQ key you paste is stored server-side instead of in your environment. ### How long does it take to connect DeployHQ to Hermes Agent? About two minutes. Sign in, click Connect next to DeployHQ in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring DeployHQ up myself? The alternative to ClawLink is usually manual credential 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 DeployHQ working from chat. ### Hermes paired but still can't use DeployHQ 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.