How to connect Appcircle to Hermes Agent
Connect Appcircle to Hermes with ClawLink: paste your Appcircle key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
AppcircleAPI KEYMCPAppcircle is an enterprise-grade mobile CI/CD platform that enables developers to build, test, and publish mobile applications efficiently, offering both cloud-based and self-hosted deployment options.. Once connected, Hermes Agent can read and act on Appcircle from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Appcircle 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 Appcircle setup: pair once in the browser and your always-on Hermes agent can act on Appcircle 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 Appcircle.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Appcircle
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Appcircle?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Appcircle in the ClawLink dashboard — paste your Appcircle API key once.
Verify the connection by asking Hermes:
Use Appcircle to distribution list profiles and walk me through the result in plain English.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Appcircle is connected in the dashboard, that agent calls the same 14 Appcircle tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Appcircle MCP for Hermes
Looking for a Appcircle MCP server for Hermes Agent? ClawLink connects Appcircle to Hermes Agent and exposes 14 Appcircle tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Appcircle integration works the same way.
What the Hermes Agent Appcircle integration can do
14 Appcircle tools are ready for Hermes Agent once the account is connected.
All 14 Appcircle tools for Hermes
| Tool | What it does |
|---|---|
Distribution list profiles appcircle_distribution_list_profiles | List all distribution profiles for the authenticated organization |
Get distribute sent profiles appcircle_get_distribute_sent_profiles | Get distinct profile names for App Sharing Report filter |
Get publish activity report appcircle_get_publish_activity_report | Retrieve the publish activity report for your organization |
List build profiles appcircle_list_build_profiles | List all build profiles for the authenticated organization |
List bundle identifiers appcircle_list_bundle_identifiers | List all bundle identifiers in Appcircle |
List organizations appcircle_list_organizations | List organizations accessible to the authenticated user |
List store profiles appcircle_list_store_profiles | List all Enterprise App Store profiles for the authenticated organization |
Store inapp list app versions appcircle_store_inapp_list_app_versions | List available app versions for the Enterprise App Store profile |
Store list profile app versions v2 appcircle_store_list_profile_app_versions_v2 | List app versions under a given store profile |
Build repo webhook callback standard appcircle_build_repo_webhook_callback_standard | Trigger Appcircle builds via Git provider webhook callbacks |
Build webhook custom integration appcircle_build_webhook_custom_integration | Triggers Appcircle builds via custom integration webhook endpoint by forwarding Git provider |
Rename variable group appcircle_rename_variable_group | Rename an environment group (variable group) in Appcircle |
Store in app auth token appcircle_store_in_app_auth_token | Fetch an access token for Enterprise App Store in-app updates |
Store in app download version with user appcircle_store_in_app_download_version_with_user | Download a specific in-app store version and attribute the download to a user for reporting |
Try it: find the Appcircle tool you need
Browse the 14 Appcircle tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Appcircle to distribution list profiles and walk me through the result in plain English.
Pull the relevant data from Appcircle, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Appcircle, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Appcircle, group them by priority, and recommend what Hermes should do next.
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 Appcircle working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Appcircle API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Appcircle 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 Appcircle. | 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 Appcircle actions to the runtime in a format your agent can reliably use. | 14 tools for Appcircle are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Appcircle 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 Appcircle in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Appcircle 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
Hermes paired but still can't use Appcircle
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 Appcircle 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 Appcircle tools
Appcircle 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 Appcircle 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.
Appcircle 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 Appcircle has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Appcircle integration?
Yes. ClawLink is the fastest way to connect Hermes to Appcircle: link your Appcircle account once in the browser and Hermes Agent can call the Appcircle API through 14 ready-made tools — no custom code or token handling.
How do I connect Appcircle 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 Appcircle in the dashboard and Hermes can use it from the next message — no config files, and the Appcircle key you paste is stored server-side instead of in your environment.
How long does it take to connect Appcircle to Hermes Agent?
About two minutes. Sign in, click Connect next to Appcircle in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Appcircle 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 Appcircle working from chat.
Hermes paired but still can't use Appcircle
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
GitHub tools
Manage repositories, issues, pull requests, and workflows
Hermes PagerDuty integration
Manage incidents, on-call schedules, and services
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.