How to connect CommCare to Hermes Agent
Connect CommCare to Hermes with ClawLink: paste your CommCare key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
CommCareAPI KEYMCPCommCare is a mobile data collection and case management platform for health and social programs.. Once connected, Hermes Agent can read and act on CommCare from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent CommCare 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 CommCare setup: pair once in the browser and your always-on Hermes agent can act on CommCare 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 CommCare.
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 CommCare
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with CommCare?"
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 CommCare in the ClawLink dashboard — paste your CommCare API key once.
Verify the connection by asking Hermes:
List the relevant items in CommCare, group them by priority, and recommend what Hermes should do next.
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 CommCare is connected in the dashboard, that agent calls the same 6 CommCare tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
CommCare MCP for Hermes
Looking for a CommCare MCP server for Hermes Agent? ClawLink connects CommCare to Hermes Agent and exposes 6 CommCare tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw CommCare integration works the same way.
What the Hermes Agent CommCare integration can do
6 CommCare tools are ready for Hermes Agent once the account is connected.
All 6 CommCare tools for Hermes
| Tool | What it does |
|---|---|
List reports commcare_list_reports | Retrieve available reports configured in a CommCare project |
Single sign on commcare_single_sign_on | Validate login credentials and retrieve user profile for a mobile worker or web user |
Create lookup table commcare_create_lookup_table | Create a new lookup table in a CommCare domain |
Create web user invitation commcare_create_web_user_invitation | Create an invitation for a new web user in CommCare |
Submit form odk compatible commcare_submit_form_odk_compatible | Submit form data using ODK-compatible endpoint for Android client compatibility |
Submit form to app commcare_submit_form_to_app | Submit an XForm to a specific CommCare application |
Try it: find the CommCare tool you need
Browse the 6 CommCare tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in CommCare, group them by priority, and recommend what Hermes should do next.
Use CommCare to single sign on and walk me through the result in plain English.
Create it in CommCare for me, then confirm the important fields before you finish.
Create it in CommCare 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 CommCare working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the CommCare API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CommCare 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 CommCare. | 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 CommCare actions to the runtime in a format your agent can reliably use. | 6 tools for CommCare are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes CommCare 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 CommCare in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the CommCare 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 CommCare
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 CommCare 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 CommCare tools
CommCare 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 CommCare 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.
CommCare 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 CommCare 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 CommCare integration?
Yes. ClawLink is the fastest way to connect Hermes to CommCare: link your CommCare account once in the browser and Hermes Agent can call the CommCare API through 6 ready-made tools — no custom code or token handling.
How do I connect CommCare 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 CommCare in the dashboard and Hermes can use it from the next message — no config files, and the CommCare key you paste is stored server-side instead of in your environment.
How long does it take to connect CommCare to Hermes Agent?
About two minutes. Sign in, click Connect next to CommCare in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring CommCare 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 CommCare working from chat.
Hermes paired but still can't use CommCare
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 GitHub integration
Manage repositories, issues, pull requests, and workflows
Hermes PagerDuty integration
Manage incidents, on-call schedules, and services
Connect 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.