Skip to main content
Glama
pmanciniq

limesurvey-mcp-server

by pmanciniq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to limesurvey-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Server for LimeSurvey

      Guiraud
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.
      -

    • libredesk-mcp

      metanmai
      A
      license
      C
      quality
      D
      maintenance
      MCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.
      54
      8 npm
      4
      MIT

    • mcp-surveys

      EzzySoft
      A
      license
      Not graded
      quality
      C
      maintenance
      Public MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.
      2
      MIT

    • Qualtrics MCP Server

      yrvelez
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides comprehensive control over the Qualtrics platform, enabling survey creation, question management, logic flows, distributions, contacts, and response exports through natural language.
      100
      58
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 27 tools

    Disambiguation4/5

    Tools are mostly grouped by resource (surveys, groups, questions, participants, responses) and the verb_noun names make their targets clear. A couple of pairs such as get_summary vs get_fieldmap and remind_participants vs mail_registered_participants could be confused, but the descriptions generally resolve the ambiguity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern like list_surveys, add_group, and delete_question. The main deviations are cpd_importParticipants, which mixes prefix and camelCase, and limesurvey_connection_test, which is a noun phrase rather than a verb-based action.

    Tool Count2/5

    With 27 tools, the server exceeds the threshold where tool selection becomes unwieldy. While LimeSurvey is a broad domain, many of these tools could be consolidated or the server split into focused sub-servers to reduce mental overhead.

    Completeness2/5

    The server covers surveys, groups, and several property operations, but key lifecycle gaps exist: there is no add_question, no response read/update/delete, no quota mutation, and no survey deactivate/export. These missing operations will cause failures in common LimeSurvey automation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources