CommCare

@CommCare list all configured reports in our maternal health project so I can see what data we're currently tracking

Here are the reports configured in your CommCare domain: 1. **Antenatal Visit Summary** (ID: anc_visits_2024) — Tracks ANC attendance by facility and week 2. **Birth Outcomes Report** (ID: birth_outcomes) — Aggregates delivery data including complications 3. **CHW Performance Dashboard** (ID: chw_metrics) — Shows form submission rates and case load by community health worker 4. **Postnatal Follow-up Tracker** (ID: pnc_followup) — Lists mothers due for postnatal visits in next 7 days This is an illustrative example showing typical report metadata. Your actual reports will vary by project configuration.

This example demonstrates the List Reports tool, which is essential for discovering what analytics are available before downloading report data. Requires 'View Reports' permission. Use this as a first step before requesting specific report downloads — the report IDs returned here are needed for subsequent data extraction calls.

@CommCare create a lookup table called 'essential_medicines' with columns for drug_name, dosage_form, and stock_threshold for our pharmacy inventory system

I've created the lookup table 'essential_medicines' in your CommCare domain with the following structure: **Table ID:** essential_medicines **Columns:** - drug_name (text) - dosage_form (text) - stock_threshold (number) The table is now available for use in your CommCare applications. You can populate it with data through the CommCare web interface or via bulk upload. Mobile workers will be able to reference this table in forms once you configure the app to use it. This is an illustrative example of the table creation response.

This example shows the Create Lookup Table tool, which sets up reference data structures that mobile workers can query in the field. Requires 'Edit Apps' permission. Important: This only creates the table schema — you'll need to populate it with actual drug data separately. Lookup tables are cached on mobile devices, so changes may take time to sync.

@CommCare invite sarah.jones@healthngo.org as a web user with report viewer access so she can monitor our field data without editing cases

I've created a web user invitation for sarah.jones@healthngo.org with the following configuration: **Email:** sarah.jones@healthngo.org **Role:** Report Viewer (read-only access to reports and dashboards) **Permissions:** View Reports, View Case Data **Status:** Invitation sent Sarah will receive an email with instructions to set her password and access the CommCare web portal. She'll be able to view configured reports and export data but cannot create or modify cases, forms, or application structure. The invitation expires in 7 days if not accepted. This is an illustrative example of the invitation creation process.

This example demonstrates the Create Web User Invitation tool for onboarding team members with specific access levels. Requires 'Edit Web Users & Edit Access API' permissions. Critical consideration: Role assignments are permanent once accepted — ensure you've selected the correct permission level before sending. Invited users consume a web user license in your CommCare subscription.

When CommCare MCP handles offline-first mobile workflows

A 12-person community health team collects patient visits on Android tablets in rural areas with spotty connectivity. The CommCare MCP is the right call here because it bridges the gap between field data collection and your team's AI workspace. Use the Submit Form ODK Compatible tool to push XForm submissions from mobile workers into Switchy threads, where a nurse manager can review flagged cases and route follow-ups without opening CommCare's web UI. The auth is straightforward—one API key scoped to form submission. The threshold: if your team needs real-time two-way sync (updating forms mid-collection), you'll hit the MCP's read-heavy limits and should keep CommCare's native app in the loop. For post-collection triage and case review, this setup cuts the manager's daily CommCare login time in half.

When batch user provisioning justifies the MCP overhead

A nonprofit scales from 8 to 40 field staff in one quarter and needs to provision CommCare accounts with role-based permissions. The Create Web User Invitation tool automates what would otherwise be 32 manual invites through CommCare's admin panel. In Switchy, an ops lead runs a prompt that reads a CSV of new hires and fires invitations with pre-set roles (data collector, supervisor, read-only). The win is speed and audit trail—all invites logged in one thread. The trade-off: if you're onboarding fewer than 10 users per month, the MCP setup (API key, permission scoping, testing) takes longer than clicking through the UI. Above 15-20 users quarterly, the MCP pays for itself in the second cohort.

When CommCare MCP replaces manual report exports

A 6-person program team sends weekly case summaries to donors who don't have CommCare logins. The List Reports and Download Report Data tools let a program manager pull configured reports into Switchy, summarize trends with AI, and draft stakeholder emails—all in one thread. The MCP handles the repetitive export step that used to require logging into CommCare, navigating to reports, downloading CSVs, and copying data into email drafts. The constraint: CommCare's report API is read-only, so if your stakeholders need to filter or pivot the data themselves, you're better off giving them direct CommCare access. For teams that own the narrative and just need the raw numbers on a schedule, this MCP turns a 20-minute weekly task into a 3-minute prompt.