Skip to main content
Glama

Related Servers

Alternatives to kobotoolbox-mcp-server

No user-submitted related servers found.

    Related Servers

    • -
      license
      B
      quality
      Not graded
      maintenance
      A comprehensive Model Context Protocol server that enables Claude Desktop users to manage Tally forms with 23 powerful tools for creating, editing, and analyzing forms, submissions, questions, webhooks, and conditional logic.
      23
      1
      -
    • F
      license
      A
      quality
      C
      maintenance
      Enables natural-language (Chinese or English) querying of a socioeconomic survey microdata warehouse covering five survey programs and over a thousand tables, by exposing standard tools for exploring surveys and sections, semantically searching variable metadata, generating read-only SQL, computing weighted statistics, and rendering charts. Results, SQL, and tool calls are returned in-chat, and it can be attached to Claude Desktop or Claude Code as well as its bundled web interface.
      14
      -

    TDQS

    A4.1/5.0

    Scored across 27 tools

    Disambiguation5/5

    Every tool targets a distinct resource+action, with cross-references clarifying adjacent purposes. kobo_list_submissions, kobo_get_data_sample, and kobo_export_submissions_excel are clearly separated as raw paged, cleaned sample, and file export; kobo_patch_form vs kobo_update_form explicitly explain targeted vs full replacement. No two tools could reasonably be confused.

    Naming Consistency4/5

    The overwhelming majority follow kobo_<verb>_<object> (kobo_create_form, kobo_list_submissions, kobo_delete_submissions). Minor deviations exist: kobo_form_versions is a noun phrase, and kobo_analyze, kobo_crosstab, kobo_doctor lack the standard verb+object structure. These are still readable and predictable within the overall convention.

    Tool Count2/5

    At 27 tools, the server lands in the 'too many' band, especially since it bundles three distinct domains: form design/deployment, submission management, and analysis/reporting. While each tool has a distinct role, the surface is heavy for agent selection and would benefit from splitting into focused form, data, and reporting servers.

    Completeness4/5

    The surface covers the full form lifecycle (create/read/update/patch/deploy/archive/clone/import/delete/versions), submission workflows (list/get/submit/validate/delete/attachments/export), and analysis (load/analyze/crosstab/data sample/report). Minor gaps include no way to update a form's name/description after creation and no submission answer editing beyond validation status, but these are generally workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues