Overview
MCP (the Model Context Protocol) is the standard way for AI assistants to use outside tools. This server gives an assistant 40-odd tools for KoboToolbox: listing projects, reading and filtering submissions, statistics, exports, attachments, form building and deployment, sharing, REST services and more.
- It acts as you. Each person signs in with their own KoboToolbox API token. The assistant sees the projects your account can see and can do what your account may do; Kobo's permissions still apply.
- Several accounts, one connection. Connect accounts on the Global and EU servers together, even with the same username on both, and add or remove them later by reconnecting. See Several accounts.
- It asks first. Tools that change something are marked as such, so clients that ask before running them will ask. The assistant is also told to confirm with you before redeploying a live form, changing submissions in bulk, sharing a project, archiving a project or sending data elsewhere.
- Deleting takes your say-so. Submissions and whole projects can be deleted, but only after the assistant has shown you exactly what would go and you have agreed to it; it cannot delete on a first call. Archiving a project is the reversible alternative, and the tools offer it first. See Deleting.
- Nothing is stored. The server has no database. Your token is sealed, encrypted, inside the connection your client holds. See Security.
It works with the Global server (kf.kobotoolbox.org) and the EU server (eu.kobotoolbox.org).
Get your API token
- Sign in to KoboToolbox.
- Open your token page: kf.kobotoolbox.org/token/ on the Global server, or eu.kobotoolbox.org/token/ on the EU server. You can also find it under Account Settings → Security → API Key.
- Copy the key. You'll paste it into the sign-in page in the next step.
The token gives full access to your account, as your password does. Paste it only into the sign-in page at https://mcp.kobolabs.dev or your own client's settings, and don't share it.
Connect
Pick your client below. Most clients sign in with OAuth: a KoboToolbox sign-in page opens, you choose your server, paste your API token and approve.
claude.ai and Claude Desktop
- Open Settings → Connectors and choose Add custom connector.
- Name it KoboToolbox and enter the URL
https://mcp.kobolabs.dev/mcp. Leave the OAuth Client ID and Secret empty. - Click Add, then Connect. The KoboToolbox sign-in page opens.
- Pick your server (Global or EU), or type another server's URL under Or another KoboToolbox server. Paste your API token and click Connect. You're sent back to Claude. To connect more than one account, see Several accounts.
- In a chat, make sure the connector is turned on in the tools menu, then ask
Which Kobo account am I connected as?
Plans: on Free plans you can add one custom connector. On Team and Enterprise plans only Owners can add connectors to the organization; members then connect it for themselves with their own token. A connector added in claude.ai also appears in Claude Desktop and the mobile apps.
Claude Code
claude mcp add --transport http kobo https://mcp.kobolabs.dev/mcp
Then run /mcp in Claude Code, choose kobo and Authenticate. The sign-in page opens in your browser. Add --scope user to make the server available in every project.
Other MCP clients
Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect: give it the URL https://mcp.kobolabs.dev/mcp. The server publishes its OAuth metadata and supports dynamic client registration, so no client ID or secret is needed. Clients that only support local (stdio) servers can't connect directly.
Scripts and clients without OAuth (header mode)
Clients that can send custom headers but don't support OAuth can pass the token on every request instead:
| Header | Value |
|---|---|
X-Kobo-Token | Your API token (or send Authorization: Token <token>) |
X-Kobo-Base-URL | Optional: global (the default), eu, or another server's URL, such as https://kobo.ifrc.org |
In Claude Code, with the token in the KOBO_TOKEN environment variable:
claude mcp add --transport http kobo https://mcp.kobolabs.dev/mcp \
--header "X-Kobo-Token: $KOBO_TOKEN"
Or in a project's .mcp.json. Keep the token itself out of version control: the file reads it from the environment.
{
"mcpServers": {
"kobo": {
"type": "http",
"url": "https://mcp.kobolabs.dev/mcp",
"headers": { "X-Kobo-Token": "${KOBO_TOKEN}", "X-Kobo-Base-URL": "global" }
}
}
}
In header mode your Kobo token travels to this server with every request, rather than being sealed once at sign-in. Use OAuth where your client supports it.
Several accounts
One connection can use up to 10 Kobo accounts, on one server or on several. An account is a username on a server, so bob on the Global server and bob on the EU server are two accounts, labelled bob@global and bob@eu.
- On the sign-in page, paste a token and click Add this account, then add another for each account, pick the default, then click Connect.
- To change the list later, connect again: in claude.ai or Claude Desktop, disconnect and reconnect the connector; in Claude Code, run
/mcp, choose kobo and sign in again. If you tick Remember these accounts on this browser, the next sign-in starts with your accounts already listed, so adding or removing one takes a single reconnect. - In header mode, send
X-Kobo-Accounts: global=<token>, eu=<token>instead ofX-Kobo-Token.
The assistant sees every connected account and says which one it's using. Name the account when it matters, as in List the projects in my EU account.
Before changing anything, it must name the account, so a change can't land on the wrong server.
Check it works
Ask Which Kobo account am I connected as?
The assistant should call whoami and reply with your username and server, or with each account if you connected several. Then try List my projects.
What you can ask
Write as you would to a colleague; the assistant picks the tools. A project can be named, or given as its uid or a link copied from KoboToolbox. Each prompt below lists the tools it should use.
Explore your projects
List my projects that got submissions this month.
list_projectsWhat's in the household survey: questions, languages and how many submissions?
get_project,describe_formWho has access to the WASH baseline, and did anyone redeploy the form in the last two weeks?
list_permissions,get_project_activity
Analyse data
Show me the last 10 submissions from the Mombasa district, with choice labels.
describe_form,get_submissionsHow many submissions per week since March, and how many are approved?
get_submission_statsSummarise the answers to the water-source and distance questions, split by enumerator.
summarize_submissionsWrite a one-page donor update on the nutrition survey: total reached, the trend by month, the share of children with MUAC under 11.5 cm by district, and which districts are behind target.
describe_form,get_submission_stats,summarize_submissions,get_submissions
Check and clean data
Are there households entered twice? Match on household ID, or on head's name plus village.
find_duplicatesFind households entered twice in the WASH baseline, matching on household ID. Show me the groups, then keep the earliest submission in each and put the rest on hold.
find_duplicates,set_validation_statusThe 'age' answers in the Kisumu batch were typed in months. Show me the ones over 120, propose corrected values in years, and once I approve, fix them.
get_submissions,edit_submissions(dry run first)Put the submissions from enumerator 'amina' on 14 June on hold.
set_validation_statusDelete the test submissions I made while piloting — the ones from 'test_enum'.
It tells you how many it found and waits for your go-ahead (see Deleting).delete_submissionsI'm finished with 'Pilot survey (old)'. Export it first, then delete the project.
create_export,delete_project
Build, change and test forms
Deploy this XLSForm as a new project called 'Market prices 2026'
(attach the .xlsx file).convert_xlsform,deploy_formDraft a household survey with a consent question that ends the form on 'no' and a repeat for each member. Show me a preview I can try before you deploy it.
preview_form,deploy_formAdd a required phone-number question after 'name' in the registration form, show me what changes, and redeploy it.
get_form_content,compare_form_versions,deploy_formMake 30 realistic dummy submissions, check the skip logic held, and check the CSV export has every column.
create_submissions,summarize_submissions,create_exportCopy the household survey from my Global account to my EU account.
(with both accounts connected)get_form_content,deploy_form
Export, share and integrate
Export only the approved submissions from Nakuru as GeoJSON for QGIS.
create_exportGive 'fatuma_k' permission to view and validate submissions on the WASH project, but not to edit the form.
share_projectShare the WASH project with the enumerators in this sheet: each can submit, but only see and edit their own province's submissions.
bulk_share_projectCopy the sharing of last year's baseline to the new endline project.
list_permissions,bulk_share_projectThe dashboard's endpoint was down yesterday. Resend whatever failed and confirm it went through.
get_hook_logs,retry_hookEmail me and the M&E lead whenever a beneficiary reports not receiving their kit.
create_email_notification,send_test_email
Live dashboards
Make a public dashboard of my sports survey, with a filter on region, and keep it up to date every 15 minutes.
create_dashboard,update_dashboard,set_dashboard_settingsAdd my round 2 project to this dashboard, merge it with round 1, and compare the rounds.
add_dashboard_source,describe_dashboard_sources,preview_dataset,update_dashboardDo a desk review on water and shelter for this dashboard: find recent OCHA and IOM figures, put them beside the survey's, and write a short cited narrative.
get_narrative_context,save_evidence,update_dashboard,publish_narrativeWhich published texts need another look since the new data came in? Update them, show me, and publish again.
get_dashboard,get_narrative_context,update_dashboard,publish_narrativeTurn my flood dashboard into a story for donors. Show me the outline first.
get_dashboard,generate_dashboard_layout,update_dashboardIn the water chapter, zoom the map to the three counties with most answers, one step each, then add a step citing the HNO figure beside our chart.
update_dashboard,publish_narrative
Built-in prompts
Your client lists these next to the tools (in Claude, under the + menu):
- Weekly digest: a summary of recent activity on a project.
- Data quality review: missing answers, duplicates, outliers and odd enumerators.
- Edit a form in the preview: change a form visually, then deploy it.
- Email alerts: set up email notifications step by step.
- Combine projects in a dashboard: bring in another round or a linked form, match up their questions and ids, and check what matched.
- Desk review for a dashboard: research secondary sources, set them beside the survey's numbers, and write cited narratives for you to publish.
- Write a story from a dashboard: an outline you approve, then the chapters and steps.
Tools
Reads tools only look. Changes tools create or change something in KoboToolbox, and several of them offer a dry_run that shows what would happen first. Deletes tools remove data permanently and can only do so after you have confirmed it (see Deleting).
| Tool | What it does |
|---|---|
| Account and projects | |
whoami | The connected accounts and their servers. |
list_projects | Your projects, with submission counts and deployment status. |
get_project | One project's details, its web form links and whether it's public. |
describe_form | The form's questions, their xpaths, choices and languages. |
get_form_content | The form's full content as JSON, ready to change and redeploy. |
get_xlsform | The form as an XLSForm. |
convert_xlsform | Preview an XLSForm as form content before deploying it. |
preview_form | Try a form in the chat before it's deployed: skip logic, constraints, cascades, repeats and languages work. Logic shows every rule in plain words, what depends on what, likely mistakes and a flowchart (also as Mermaid text). Edit form and Edit rules change the form right in the preview; the agent deploys your changes after you confirm. Needs a chat app with MCP Apps support for the interactive preview. |
compare_form_versions | What changed between two versions, or what a redeploy would change. |
get_project_activity | Who did what on a project, and when. |
list_permissions | Who a project is shared with, what they may do, and which submissions they see. |
| Submissions and statistics | |
get_submissions | Submissions, filtered with a query, with chosen fields, sorting and choice labels. |
get_submission_count | How many submissions match a filter. |
get_submission | One submission. |
get_submission_stats | Totals, counts per day, week or month, and the validation breakdown. |
summarize_submissions | Per question: missing rates, choice counts, numeric ranges and quartiles, map extent; optionally per enumerator. |
find_duplicates | Records entered twice, matched on the fields you choose. |
get_enketo_link | A link to open a submission in Enketo to view or edit it. |
| Files and exports | |
list_attachments | The photos, audio and other files attached to submissions. |
get_attachment | One attachment; images come back as images. |
export_data | Submissions as CSV, straight into the conversation. |
create_export Changes | An xlsx, CSV, GeoJSON, KML or SPSS export, optionally filtered, as a download link. |
list_exports | Earlier exports and their links. |
list_form_media | Files attached to the form, such as CSV choice lists. |
upload_form_media Changes | Add or replace a form media file (CSV, image, audio, or a link to a hosted file). |
| Forms and projects | |
deploy_form Changes | Create or update a form from JSON or an XLSForm, and deploy it. |
clone_project Changes | Copy a project, for example as a training copy. |
archive_project Changes | Stop data collection, or restart it. |
delete_project Deletes | Delete a project and all its data, for good. Asks you to confirm first (see Deleting). |
share_project Changes | Set what one user, or the public, may do on a project, including which submissions they see. |
bulk_share_project Changes | Set many users' access at once, for example from a spreadsheet, with a preview first. |
| Changing submissions | |
create_submissions Changes | Add real or dummy submissions, with files. Dummy data follows the form's skip logic and constraints. |
duplicate_submission Changes | Copy a submission. |
edit_submissions Changes | Edit answers in bulk. |
set_validation_status Changes | Approve, reject or put on hold, by ids or by filter. |
add_transcript Changes | Save a transcript or translation of an audio or video answer. |
delete_submissions Deletes | Delete submissions, by ids or by filter, for good. Asks you to confirm first (see Deleting). |
| REST services | |
list_hooks | The REST services a project sends submissions to. |
get_hook_logs | Delivery results, including failures. |
create_hook Changes | Send every new submission to another server. |
update_hook Changes | Pause, resume, re-point or change a service's credentials. |
retry_hook Changes | Resend failed deliveries. |
| Email notifications | |
create_email_notification Changes | Email people about new submissions. See Email alerts. |
preview_email_notification | Show the email a submission would produce, without sending it. |
send_test_email Changes | Send one test email. |
get_email_notification | A notification's recipients, template and conditions. |
update_email_notification Changes | Change or pause a notification. |
| Live dashboards | |
create_dashboard Changes | Make a live dashboard of a project you own or manage, with a first layout. See Live dashboards. |
generate_dashboard_layout Changes | Replace a dashboard's layout with one generated from the form, or with a story's outline. |
get_dashboard | A dashboard's layout, status, and the answers it shows as written. |
list_dashboards | Your dashboards and their links. |
add_dashboard_source Changes | Add another project you own or manage to a dashboard, such as a later round of the survey. |
describe_dashboard_sources | Before combining a dashboard's projects: their fields side by side, which look the same, which codes differ, and which ids could link them (and how many match). |
preview_dataset | Try combining a dashboard's projects (rounds appended, questions renamed, codes recoded, duplicates merged, records linked by an id, a repeat's entries counted per submission) and see what it finds, before saving it. |
put_dashboard_table Changes | Store a small table (targets, a code list) for dashboards to read; lists of people go through the dashboards admin page instead. |
set_table_columns Changes | Fix a table's column kinds, labels or choice labels. |
list_dashboard_tables | Your tables, uploaded or stored, with their columns and first rows. |
add_dashboard_table Changes | Let a dashboard read one of your tables, to show it or join it to a project. |
list_espo_connections | Your EspoCRM connections (added in the dashboards admin page) and the feeds made through them. |
create_espo_feed Changes | Keep an EspoCRM entity's records (sites, activities) as a table that follows EspoCRM, for dashboards to read. |
update_espo_feed Changes | Change a feed's fields, filters or how often it's read. |
remove_dashboard_source Changes | Stop a dashboard reading one of its projects. Nothing in KoboToolbox changes. |
update_dashboard Changes | Add, change, move or remove charts, pages and filters; set the style. |
set_dashboard_settings Changes | Publish (public or password) or take offline; how often it refreshes. |
refresh_dashboard Changes | Check KoboToolbox for new data now. |
fetch_dashboard_boundaries Changes | Get a country's regions or districts, or the countries of the world, as a map layer, to shade maps and group locations by area. |
get_dashboard_data | The numbers a dashboard page shows right now. |
save_evidence Changes | Save sources from desk research, and findings that quote them, to your evidence library. Every figure must be in its quote. |
list_evidence | Your evidence library: sources and findings, by theme or source. |
archive_evidence Changes | Stop a source or finding being cited (restorable). |
get_narrative_context | What a narrative can use: each widget's live numbers as placeholders, and your evidence library. |
publish_narrative Changes | Publish a dashboard's narratives, after showing you how they read (asks first). |
withdraw_narrative Changes | Take a published narrative off the dashboard; its draft stays. |
list_dashboard_revisions | A dashboard's layout history. |
revert_dashboard Changes | Bring back an earlier layout. |
delete_dashboard Changes | Delete a dashboard (asks first; Kobo data is untouched). |
Deleting
KoboToolbox has no trash: a deleted project or submission is gone at once, with its attachments, and nothing can bring it back. So the two delete tools can't act on their own.
- The assistant has to ask first. Its first call deletes nothing. It only gets back what would go — the project's name, how many submissions, who else can see it — and a confirmation that lasts ten minutes.
- You approve an exact number. The confirmation is tied to that project and those submissions. If a submission arrives, or the assistant aims at anything else, the delete is refused and you are asked again.
- Reversible options come first. The tools point the assistant at
archive_project(stops data collection, keeps everything, can be undone), an export to keep the data, andset_validation_statusto mark bad records instead of removing them. - Permissions still apply: deleting submissions needs
delete_submissionson the project, and deleting a project means owning it.
If you would rather this server could never delete anything, connect with a KoboToolbox account that has no delete permissions, or ask your client to block the two tools.
Live dashboards
Make a public dashboard of my sports survey and keep it up to date.
The assistant builds a dashboard of a project you own, or one you have "Manage project" permission on, hosted at https://dash.kobolabs.dev. It checks KoboToolbox for new submissions on a schedule you choose, and anyone with it open sees the numbers change without reloading.
- A separate account reads the data. Make a second KoboToolbox account for dashboards (for example
you_dash). The assistant shares the project with it, view-only, and you paste that account's token into the dashboards admin page once. Your own token is never stored there. - Public or password. Dashboards start offline. The assistant can make one public; for a password, you set it in the admin page, never in the chat. Changing it signs everyone out.
- What it shows. Charts show counts and percentages. Tables, free-text answers and fine-grained maps show answers as written: the admin page and
get_dashboardlist them, so check before making a dashboard public. - Styles.
Give it the ocean style, always dark.
Pick one of five looks in KoboToolbox's colours, in light or dark, in conversation or in the admin page. A style changes the page around the charts, never which colour stands for which answer. - Tooltips.
When someone hovers over a district, show its average household size.
Choose what hovering a chart shows, add values worked out from each bar's or area's own submissions, or turn tooltips off. Small groups stay hidden, and the values are in the chart's table too. - Severity by area.
Shade the districts by how damaged housing is, and show every sector's severity by district, worst first.
An area map shaded by a measure of each area's answers, and a heatmap of several questions across districts or any other grouping, with each cell's value written in it. - Combining projects.
Add my round 2 project, merge it with round 1, and link it to the beneficiary list.
A dashboard can read several projects you own or manage, and tables you upload or the assistant stores: rounds appended and compared, questions renamed between rounds matched up, records linked on an id typed differently in each, a repeat group counted per household. The assistant shows you what it found (codes that didn't match, ids not found) before saving; the Combine projects prompt walks it through this. - Desk research.
Find recent OCHA and IOM figures on water and shelter for this survey's area.
The assistant researches with its own tools and saves each source, with the passages it quotes, to your evidence library (save_evidence). A figure that isn't in its quote is refused, so none is rounded or invented. You can check and archive them on the dashboards admin page's Evidence page. The Desk review for a dashboard prompt walks it through research, comparison and writing. - Narratives.
Add a short narrative on water, citing what you found.
The assistant writes text whose survey numbers are placeholders filled from the live data, and whose other figures cite the findings they come from, numbered, with the sources under the text. Any number that isn't from either is flagged. A narrative is a draft only you see until the assistant shows you how it reads and you say to publish it; viewers then keep that text, with its numbers up to date, until it is published again or withdrawn. When new data moves its numbers past a threshold, or a source it cites is edited,get_dashboardand the admin page flag it for review, and viewers see when it was written. - Side by side.
Put the HNO figure beside our water chart.
A source's figure can sit beside a number, a bar (as a tick at its share), a tile or a map area, with its citation; a share only ever beside a share. The assistant can also write an assessment of how the survey and the sources compare, with a verdict you agree with, shown as the author's. - Stories.
Turn my flood dashboard into a story for donors.
A dashboard can read as one scrolling page instead, a story map: a cover, then chapters, with charts and maps that stay pinned while short passages scroll past, each step highlighting answers or moving the map to an area. Its numbers stay live, filters live in an explore chapter, and steps can be cited narratives from your desk research, published like any other. The Write a story from a dashboard prompt walks the assistant through an outline you approve first. Photos for its cover are uploaded in the admin page, never through the chat. - Undo. Every layout change is kept, and
revert_dashboardbrings an earlier one back. Deleting a dashboard asks first and never touches your Kobo data.
The dashboards guide covers the rest: widgets, calculated fields, areas from locations, cross-filtering, the layout editor, tooltips, heatmaps, styles, stories, combining projects, desk research and narratives, and sharing.
Email alerts
Email the respondent and me whenever someone submits, with their name and district, but only when consent is yes.
The assistant sets up a REST service that sends each new submission to this server, which writes the email and sends it.
- Recipients can be fixed addresses, the answer to an email question in the form, or both. Each address taken from an answer gets its own email, so respondents don't see the team's addresses or each other's.
- The subject and body take placeholders:
{{ xpath }}inserts an answer and{{ xpath | label }}a choice's label;{{ @all }}lists every answer and{{ @link }}links to the project's data;{{ _id }},{{ _submission_time }},{{ _submitted_by }}and{{ _geolocation }}give the submission's details. - Conditions:
only_iflimits which submissions send an email, for example only when severity is high. - Sender: emails come from
[email protected]as “your username via KoboToolbox”, and replies go to your Kobo account's email address. - What triggers them: only new submissions, not edits or older ones.
- Limits: 200 emails a day per notification, and 1000 per account.
- Public forms: on a form anyone can submit to, emailing addresses taken from answers must be turned on explicitly.
- Pausing: ask the assistant to pause the alert (
update_email_notificationwithactive: false).
Ask the assistant to preview the email for a real submission and send you a test before it turns the alert on.
Limits
| What | Limit |
|---|---|
| Submissions per page | 1000 (the assistant pages through more) |
| Text per result | About 200 KB; longer results are cut off, and the result says so |
| Attachments | 5 MB each, and 20 MB of files per create_submissions call |
| Changes per call | 100 new submissions, or 1000 edited, validated or deleted ones (by filter there is no limit) |
| Delete confirmations | Valid for 10 minutes, for that one target only |
| Statistics | Read up to 20 000 submissions |
| Sign-in | Access tokens last 1 hour and renew automatically; after 30 days without use, sign in again |
Security and privacy
- The sign-in page accepts your API token, never your password. It checks the token with your KoboToolbox server, then seals it, using AES-GCM encryption, inside the tokens it gives your client.
- Nothing is stored. There's no database: your token lives only inside those encrypted tokens, which only this server can open. Access tokens last 1 hour and refresh tokens 30 days. Each refresh re-checks your Kobo token; old refresh tokens stop working once used. With several accounts, each token is re-checked, and an account whose token KoboToolbox refuses is dropped.
- “Remember these accounts” is opt-in. It keeps your account list, sealed the same way, in a cookie on your own browser for 30 days. The cookie is HttpOnly and sent only to the sign-in page. The server still stores nothing. Leave it unticked on a shared computer; Forget the accounts saved on this browser on the sign-in page clears it.
- Other servers can't reach private networks. For a KoboToolbox server it doesn't list, this server looks up the address on every connection and connects only to public addresses. It does the same for redirects, such as to attachment storage.
- Your token goes only to your Kobo server. Requests to any other host, such as a redirect or an attachment stored elsewhere, are sent without it. It never appears in logs, errors or tool results.
- Assistants act as you. They can do anything your account may do with the tools above, including editing data, so review what the assistant proposes before you approve changes.
- Deleting needs your confirmation. The two delete tools can't act on a first call: they hand back what would go plus a confirmation that only works for that exact target and expires after ten minutes. See Deleting.
- Email alerts keep their settings in Kobo, sealed with a server key, so project editors can't change the recipients there. Like any REST service, they send each new submission out of Kobo: here, to this server and to the email provider (Resend). None of it is stored or logged.
- The sign-in page is protected against cross-site request forgery and framing, and is rate-limited.
Revoke access
- Everywhere, straight away: regenerate your API token in KoboToolbox (Account Settings → Security). Calls using the old token fail from then on, and your clients will ask you to sign in again.
- One account: regenerate that account's token. The account is dropped from your connections at the next refresh, within an hour, and your other accounts keep working.
- One client: remove the connector in claude.ai or Claude Desktop settings, or run
claude mcp remove koboin Claude Code.
Help and troubleshooting
“Project not found”, or my projects are missing
The most common cause is the wrong server. Accounts on the Global server (kf.kobotoolbox.org) and the EU server (eu.kobotoolbox.org) are separate. Ask Which Kobo account am I connected as?
to check, and reconnect with the other server if needed. If you connected several accounts, say which one, as in in my EU account
.
The sign-in page says the token wasn't accepted
Check that you picked the server your account is on, and that you copied the whole API key (not your password). If you regenerated the token recently, copy the new one.
“This sign-in link has expired or isn't valid”
Sign-in links last 10 minutes. Go back to your client and start the connection again.
My account is on another KoboToolbox server
On the sign-in page, type your server's address under Or another KoboToolbox server, for example https://kobo.ifrc.org, and get your API token from that server's /token/ page. The server must be reachable from the internet over https; servers on a private network can't connect. The account is then labelled with the server's name, such as [email protected].
I can't add a custom connector in Claude
Free plans allow one custom connector, so you may need to remove another one first. On Team and Enterprise plans, ask an Owner to add the connector to your organization; you then connect it yourself with your own token.
The assistant doesn't use the KoboToolbox tools
Make sure the connector is turned on for the conversation (in Claude, in the tools menu under the message box), and mention KoboToolbox or a project by name in your request.
One of my accounts disappeared from the connection
When KoboToolbox stops accepting an account's token, for example after you regenerated it, the server drops that account at the next refresh. Connect again and add the account with its current token. If you ticked “Remember”, the sign-in page names the account it removed.
I was asked to sign in again
That happens after 30 days without use, or when your Kobo token has changed. Sign in again with your current token.
Where do I get help with KoboToolbox itself?
The KoboToolbox Help Center covers forms, projects and data, and the community forum is the place for questions.