io.github.drannakurasova/kobotoolbox-mcp-server (MCP)

This MCP server provides integration for KoboToolbox. It supports operations to list available forms, fetch submissions, and export field data, enabling developers to retrieve and work with KoboToolbox content through MCP-compatible tooling. The server is identified by the slug io-github-drannakurasova-kobotoolbox-mcp-server.

🛠️ Key Features

List forms
Fetch submissions
Export field data

🚀 Use Cases

Discover KoboToolbox forms
Pull submission data for downstream processing
Export field-level data from KoboToolbox for analysis or import

⚠️ Limitations

Capabilities described are limited to forms listing, submissions retrieval, and field data export

KoboToolbox MCP Server

A Model Context Protocol server that lets Claude (or any MCP client) read and export field data directly from KoboToolbox.

Ask in plain language — "How many intakes came in this week that need medical attention?" or "Export this project's data as a CSV" — and the assistant queries the live KoboToolbox API and answers from real records, instead of you logging in and clicking through the dashboard by hand.

As of July 2026, no KoboToolbox MCP server existed in the official MCP registry — this is the first.

Why KoboToolbox

KoboToolbox is the most widely used data-collection toolkit in humanitarian and development work. It's open-source, free to use, and runs the field operations of UNHCR and thousands of NGOs — surveys, needs assessments, monitoring — often in places with poor connectivity and no dedicated IT staff.

That last part is exactly why an MCP server matters here. The organizations running on KoboToolbox are the ones least likely to have engineers who can pull and analyze their own data on demand. Today, answering "what does this month's data actually say?" means a person logging in, filtering submissions by hand, exporting a spreadsheet, and counting. This server collapses that into a question typed in chat — and turns any MCP-capable assistant into someone who can operate the tool on the team's behalf.

There are already thousands of MCP servers for developer tooling and office apps. There were none for the platform that humanitarian responders actually run their work on. This closes that gap.

What it does

Three tools, mapped directly onto the KoboToolbox REST API v2. All read/export — this server never modifies or deletes your data.

Tool	What it does	Key inputs
`list_forms`	Lists every form/project in the connected account — name, UID, deployment status, submission count.	(none)
`get_submissions`	Fetches the submitted records for one form, with optional filtering, sorting, and pagination.	`assetUid` (required), `query`, `limit`, `start`, `sort`
`export_form_data`	Kicks off a server-side export, waits for it to finish, and returns a download URL.	`assetUid` (required), `format` (`csv`/`xls`/`geojson`/`spss_labels`), `fields`

Requirements

Node.js 18+
A KoboToolbox account (free — sign up) on either the global server (kf.kobotoolbox.org) or the EU server (eu.kobotoolbox.org)
Your account's API token

Getting your API token

Log into KoboToolbox, then either:

Account Settings → Security → Display your API key, or
visit https://<your-server>/token/?format=json

Treat this token like a password — it grants full access to your account's data.

Installation

bash

git clone https://github.com/drannakurasova/kobotoolbox-mcp-server.git
cd kobotoolbox-mcp-server
npm install
npm run build

Configuration

Copy the example env file and fill in your token:

bash

cp .env.example .env

env

KOBO_API_TOKEN=your_kobotoolbox_api_token_here
KOBO_SERVER=kf.kobotoolbox.org      # or eu.kobotoolbox.org

Usage

With Claude Desktop

Add this to your claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

json

{
  "mcpServers": {
    "kobotoolbox": {
      "command": "node",
      "args": ["/absolute/path/to/kobotoolbox-mcp-server/dist/index.js"],
      "env": {
        "KOBO_API_TOKEN": "your_token_here",
        "KOBO_SERVER": "kf.kobotoolbox.org"
      }
    }
  }
}

Fully quit and reopen Claude Desktop. The kobotoolbox tools will appear in the tools menu, and you can just ask:

"What forms are in my KoboToolbox account?" "Show me the latest 10 submissions for the intake form." "Export that project's data as a CSV."

With the MCP Inspector

The Inspector is a browser-based test harness — the quickest way to exercise each tool directly (and to record a demo).

bash

npm run inspect

It prints an authenticated URL; open it, click List Tools, select a tool, fill in the inputs, and hit Run Tool.

Development

bash

npm run dev       # run from source with tsx (no build step)
npm run build     # compile TypeScript to dist/
npm start         # run the compiled server
npm run inspect   # launch the MCP Inspector against the built server

How it works

src/index.ts — defines the MCP server and registers the three tools, with input validation via Zod. Runs over stdio.
src/kobo-client.ts — a thin, typed wrapper around the KoboToolbox REST API v2 (token auth, form listing, submission fetch, and the create-then-poll export flow).

Credentials come only from environment variables — nothing is hardcoded, so the same server works against any KoboToolbox account or form.

Roadmap

Possible extensions:

Write access (create submissions, edit validation status)
Per-form schema/question introspection so the assistant understands field meanings
Support for private/self-hosted KoboToolbox instances

License

MIT