KoboToolbox

@KoboToolbox list all survey projects deployed in the last 30 days and show me their submission counts

Found 4 deployed survey projects from the past month: 1. **Community Health Baseline** (deployed Jan 15) — 127 submissions 2. **Water Access Survey Q1** (deployed Jan 22) — 89 submissions 3. **School Enrollment Tracker** (deployed Feb 3) — 203 submissions 4. **Market Vendor Registration** (deployed Feb 8) — 45 submissions All projects are currently accepting responses. The School Enrollment Tracker has the highest response rate at ~14 submissions per day.

This example uses List Assets filtered by deployment date and combines it with submission metadata. Requires read permissions on all listed projects. The MCP returns paginated results; if your account has many assets, you may need to request additional pages or narrow the date range.

@KoboToolbox export all submissions from the Water Access Survey project as CSV and give me the download link

Export initiated for **Water Access Survey Q1** (UID: aXk9mPqR3nL7). Waiting for KoboToolbox to generate the CSV file... Export completed in 8 seconds. **Download URL:** https://kf.kobotoolbox.org/exports/aXk9mPqR3nL7_submissions_2025-02-12.csv This link contains 89 submissions with all form fields. The file expires in 7 days. You can re-run this export anytime to get fresh data.

This example demonstrates the Export Submissions tool, which creates an asynchronous job and polls until ready. Large datasets (1,000+ submissions) can take several minutes. The returned URL requires your KoboToolbox session to download; share cautiously if the survey contains sensitive data.

@KoboToolbox create a new draft survey called Household Income Study by cloning the Community Health Baseline project, then summarize what fields it inherited

Created draft project **Household Income Study** (UID: bQp4nXs8tYv2) by cloning Community Health Baseline. Inherited form structure: - **Section 1: Demographics** — 6 questions (age, gender, household size, location) - **Section 2: Health Access** — 4 questions (clinic distance, insurance status) - **Section 3: Economic Indicators** — 3 questions (income bracket, employment type) The draft is not yet deployed. You can edit the form in KoboToolbox or ask me to deploy it when ready.

This example chains Create Project (with clone option) and Get Project to show inherited structure. The cloned draft retains all form logic and skip patterns from the source. You must deploy the project separately before it accepts submissions; cloning does not auto-deploy.

When KoboToolbox MCP bridges field teams and analysis

A 6-person nonprofit runs quarterly health surveys across rural clinics. Field staff collect responses on tablets via KoboToolbox forms; the program team needs those submissions in Switchy to generate donor reports and flag anomalies. The MCP's Export Submissions tool pulls completed surveys into the workspace where analysts can query them alongside budget sheets and previous quarters. This works when your survey cadence is weekly or slower—KoboToolbox's async export takes 30-90 seconds per job, so real-time dashboards aren't realistic. If your team reviews submissions within 24 hours of collection and needs to cross-reference them with other datasets, this MCP eliminates the CSV-download-upload ritual. API key auth means one workspace admin provisions access; no per-user OAuth friction.

Managing draft-to-deployment cycles in shared workspaces

A 3-person research consultancy designs client surveys collaboratively. One person drafts the form in KoboToolbox's UI, another reviews it in Switchy using Get Project to inspect question logic and skip patterns, then a third deploys it with Deploy Project once the client approves. The MCP's 9 tools cover the full lifecycle—create, retrieve, deploy, delete—so the team never leaves Switchy to coordinate. This breaks down if you're iterating on forms hourly; KoboToolbox doesn't version-control form edits the way GitHub does code, so rapid changes create confusion about which draft is current. For teams running 2-5 survey projects concurrently with weekly review cycles, the MCP keeps deployment decisions visible and auditable in one workspace.

When individual submission lookup justifies the integration

A 4-person customer feedback team receives 200 survey responses daily through KoboToolbox. Most are routine, but 10-15 need escalation to product or support. The team uses Get Submission to pull flagged responses into Switchy threads where they attach context from Slack, Linear, and CRM notes before routing. This scenario only makes sense if your triage process requires stitching KoboToolbox data with 2+ other tools in the same conversation—if you're just reading submissions, KoboToolbox's native UI is faster. The MCP's value is in the handoff: a support agent sees a submission UUID in Slack, pastes it into Switchy, and the full response appears alongside the customer's ticket history. Single API key for the whole team means no per-agent provisioning.