CommCare for AI agents
CommCare is a mobile data collection platform for health and social programs, letting field workers submit forms and manage cases from a phone. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in CommCare.
Submit a completed form
Submit a completed field form to an application, updating the relevant case record.
Check submitted reports
Pull a report to see submitted forms and case data for a program.
Create a web user invitation
Create an invitation for a new web user to access a program's data.
6 CommCare actions, graded by risk.
Every CommCare action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- commcare.list_reportsList Reports
write
5Create and change things. Allow, or ask the user first.
- commcare.create_lookup_tableCreate Lookup Table
- commcare.create_web_user_invitationCreate Web User Invitation
- commcare.single_sign_onSingle Sign On
- commcare.submit_form_to_appSubmit Form to Application
- commcare.submit_form_odk_compatibleSubmit Form ODK Compatible
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
CommCare in three steps.
- 01Your users connect CommCareThey add their CommCare api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Lookup Table” can wait for the user to approve.
- 03Any agent can actYour agent calls CommCare through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('commcare', { read: 'allow', write: 'ask', // create_lookup_table destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How CommCare connects.
Users add their CommCare api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same CommCare connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use CommCare from any agent.
CommCare and Arc0, answered.
Can I use CommCare with Claude, ChatGPT or Cursor?
Yes. Connect CommCare to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the CommCare actions you allow.
How do users connect CommCare?
Users add their CommCare api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which CommCare actions can my agent take?
6 in total: 1 read, 5 write and 0 destructive, such as “create Lookup Table”. Your policies decide which of them each agent may call.
Can I make my agent read-only in CommCare?
Yes. Allow read actions and deny writes in the CommCare policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call CommCare too?
Yes. The same CommCare connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug CommCare into your agent.
Your users connect CommCare once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan