LimeSurvey MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_responseC | Add a response to a LimeSurvey survey. |
| add_responsesC | Add multiple responses to a LimeSurvey survey. |
| update_responseC | Update a response in a LimeSurvey survey. |
| delete_responseC | Delete a response from a LimeSurvey survey. |
| save_responsesC | Save responses for a LimeSurvey survey. |
| export_responsesC | Export responses from a LimeSurvey survey. |
| export_statisticsC | Export statistics for a LimeSurvey survey. |
| export_timelineB | Export timeline for a LimeSurvey survey. |
| add_surveyC | Add a new LimeSurvey survey. |
| copy_surveyB | Copy a LimeSurvey survey. |
| delete_surveyC | Delete a LimeSurvey survey. |
| activate_surveyB | Activate a LimeSurvey survey. |
| import_surveyB | Import a LimeSurvey survey. |
| set_survey_propertiesC | Set LimeSurvey survey properties. |
| add_groupC | Add a group to a LimeSurvey survey. |
| delete_groupB | Delete a group from a LimeSurvey survey. |
| set_group_propertiesC | Set LimeSurvey group properties. |
| import_groupC | Import a group to a LimeSurvey survey. |
| delete_questionC | Delete a question from a LimeSurvey survey. |
| set_question_propertiesC | Set LimeSurvey question properties. |
| import_questionC | Import a question to a LimeSurvey survey. |
| add_languageC | Add a language to a LimeSurvey survey. |
| delete_languageB | Delete a language from a LimeSurvey survey. |
| set_language_propertiesC | Set LimeSurvey language properties. |
| add_participantsC | Add participants to a LimeSurvey survey. |
| delete_participantsC | Delete participants from a LimeSurvey survey. |
| invite_participantsB | Invite participants to a LimeSurvey survey. |
| set_participant_propertiesC | Set LimeSurvey participant properties. |
| import_cpdb_participantsC | Import participants from the central participant database. |
| activate_tokensC | Activate tokens for a LimeSurvey survey. |
| add_quotaC | Add a quota to a LimeSurvey survey. |
| delete_quotaC | Delete a LimeSurvey quota. |
| set_quota_propertiesC | Set LimeSurvey quota properties. |
| upload_fileC | Upload a file to a LimeSurvey survey. |
| download_filesB | Download files from a LimeSurvey survey. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_survey_statistics_and_timeline | Summarize survey statistics and submission timeline for analysis. Args: sid: The survey ID to analyze. days_back: Number of days back from today to analyze. Defaults to 30. Returns: A concise summary of survey statistics and timeline data. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| survey:// | |
| survey-group:// | |
| language:// | |
| language://default | |
| server://version | |
| server://db_version | |
| server://site_name | |
| server://users |
TDQS
Scored across 35 tools
Most tools are clearly distinct, targeting specific resources like surveys, groups, participants, questions, quotas, responses, and files with precise actions. However, some potential overlap exists between 'add_response' and 'save_responses', and 'add_participants' and 'import_cpdb_participants', which could cause minor confusion for agents.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'activate_survey', 'add_group', 'delete_participants', 'export_responses', 'import_survey', and 'set_question_properties'. This uniformity makes the tool set predictable and easy to navigate.
With 35 tools, the count is high but may be justified for a comprehensive survey management system like LimeSurvey, covering CRUD operations for multiple entities. However, it borders on being heavy and could overwhelm agents, suggesting some consolidation might improve usability.
The tool set provides extensive coverage for LimeSurvey's domain, including full lifecycle management for surveys, groups, questions, participants, responses, quotas, and files. It supports activation, import/export, property setting, and deletion, with no obvious gaps for core workflows.