limesurvey-mcp-server
Related Servers
Alternatives to limesurvey-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA simple server that enables management of LimeSurvey surveys and responses through MCP client integration.355Apache 2.0
- AlicenseBqualityAmaintenanceMCP server for LimeSurvey that provides 68 tools to interact with the LimeSurvey RemoteControl API, including survey management, participant handling, and responsive theme generation.7126 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.-
- AlicenseCqualityDmaintenanceMCP 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.5410 npm4MIT
- AlicenseNot gradedqualityBmaintenancePublic MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.2MIT
- FlicenseAqualityCmaintenanceA 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.10054-
TDQS
Scored across 27 tools
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.
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.
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.
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.