F
licenseNot graded
qualityD
maintenanceEnables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.
-
LimeSurvey MCP Server
Allows management of LimeSurvey surveys and responses through a connection to a LimeSurvey instance, enabling programmatic access to survey data and administration capabilities.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LimeSurvey MCP Server list all active surveys"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LimeSurvey MCP Server
This is an MCP server for LimeSurvey. It is a simple server that allows you to manage your LimeSurvey surveys and responses.
Configuration
Name | Description |
LIMESURVEY_URL | The URL of your LimeSurvey instance, e.g. |
LIMESURVEY_USERNAME | Your LimeSurvey username |
LIMESURVEY_PASSWORD | Your LimeSurvey password |
Related MCP server: whmcs-mcp-server
Using with MCP clients
{
"mcpServers": {
"limesurvey-mcp": {
// For example, /Users/<YOUR USERNAME>/.local/bin/uv
"command": "/path/to/uv",
"args": [
"--directory",
// For example, /Users/<YOUR USERNAME>/mcp-servers/limesurvey-mcp
"/path/to/limesurvey-mcp",
"run",
"main.py"
],
"env": {
// see config above
// "LIMESURVEY_URL": "https://myinstance.limequery.com/admin/remotecontrol"
// "LIMESURVEY_USERNAME": "myusername"
// "LIMESURVEY_PASSWORD": "mypassword"
}
}
}
}Available Tools
35 toolsactivate_surveyB
Activate a LimeSurvey survey.
Args:
sid: The survey ID.
Inputs: sid (required).
activate_tokensC
Activate tokens for a LimeSurvey survey.
Args:
sid: The survey ID.
Inputs: sid (required).
add_groupC
Add a group to a LimeSurvey survey.
Args:
sid: The survey ID.
group_data: The group data.
Inputs: sid (required), group_data (required).
add_languageC
Add a language to a LimeSurvey survey.
Args:
sid: The survey ID.
language: The language code.
Inputs: sid (required), language (required).
add_participantsC
Add participants to a LimeSurvey survey.
Args:
sid: The survey ID.
participant_data: The participant data.
Inputs: sid (required), participant_data (required).
add_quotaC
Add a quota to a LimeSurvey survey.
Args:
sid: The survey ID.
quota_data: The quota data.
Inputs: sid (required), quota_data (required).
add_responseC
Add a response to a LimeSurvey survey.
Args:
sid: The survey ID.
response: The response to add.
Inputs: sid (required), response (required).
add_responsesC
Add multiple responses to a LimeSurvey survey.
Args:
sid: The survey ID.
responses: The responses to add.
Inputs: sid (required), responses (required).
add_surveyC
Add a new LimeSurvey survey.
Args:
survey_data: The survey data.
Inputs: survey_data (required).
copy_surveyB
Copy a LimeSurvey survey.
Args:
sid: The source survey ID.
new_name: The name for the new survey.
Inputs: sid (required), new_name (required).
delete_groupB
Delete a group from a LimeSurvey survey.
Args:
sid: The survey ID.
gid: The group ID.
Inputs: sid (required), gid (required).
delete_languageB
Delete a language from a LimeSurvey survey.
Args:
sid: The survey ID.
language: The language code.
Inputs: sid (required), language (required).
delete_participantsC
Delete participants from a LimeSurvey survey.
Args:
sid: The survey ID.
tokens: The participant tokens.
Inputs: sid (required), tokens (required).
delete_questionC
Delete a question from a LimeSurvey survey.
Args:
qid: The question ID.
Inputs: qid (required).
delete_quotaC
Delete a LimeSurvey quota.
Args:
id: The quota ID.
Inputs: id (required).
delete_responseC
Delete a response from a LimeSurvey survey.
Args:
sid: The survey ID.
response_id: The response ID.
Inputs: sid (required), response_id (required).
delete_surveyC
Delete a LimeSurvey survey.
Args:
sid: The survey ID.
Inputs: sid (required).
download_filesB
Download files from a LimeSurvey survey.
Args:
sid: The survey ID.
file_id: The file ID. If None, download all files.
Inputs: sid (required), file_id.
export_responsesC
Export responses from a LimeSurvey survey.
Args:
sid: The survey ID.
file_format: The format to export (csv, json, etc).
language: The language to export (en, es, etc).
heading_type: The type of heading to export (code, full, abbreviated).
Inputs: sid (required), file_format, language, heading_type.
export_statisticsC
Export statistics for a LimeSurvey survey.
Args:
sid: The survey ID.
document_type: The document type (pdf, xls, html).
Inputs: sid (required), document_type.
export_timelineB
Export timeline for a LimeSurvey survey.
Args:
sid: The survey ID.
period: The granularity level for aggregation submission counts ('day' or 'hour').
start_date: The start datetime (YYYY-MM-DDTHH:MM:SS) in any valid ISO 8601 format.
end_date: The end datetime (YYYY-MM-DDTHH:MM:SS) in any valid ISO 8601 format.
Inputs: sid (required), period (required), start_datetime (required), end_datetime.
import_cpdb_participantsC
Import participants from the central participant database.
Args:
sid: The survey ID.
attributes: The attributes to filter participants.
Inputs: sid (required), attributes (required).
import_groupC
Import a group to a LimeSurvey survey.
Args:
sid: The survey ID.
group_file: The group file content (base64 encoded).
group_name: The name for the imported group.
Inputs: sid (required), group_file (required), group_name.
import_questionC
Import a question to a LimeSurvey survey.
Args:
sid: The survey ID.
gid: The group ID.
question_file: The question file content (base64 encoded).
Inputs: sid (required), gid (required), question_file (required).
import_surveyB
Import a LimeSurvey survey.
Args:
survey_file: The survey file content (base64 encoded).
survey_name: The name for the imported survey.
Inputs: survey_file (required), survey_name.
invite_participantsB
Invite participants to a LimeSurvey survey.
Args:
sid: The survey ID.
tokens: The participant tokens. If None, invite all participants.
Inputs: sid (required), tokens.
save_responsesC
Save responses for a LimeSurvey survey.
Args:
sid: The survey ID.
data: The response data to save.
Inputs: sid (required), data (required).
set_group_propertiesC
Set LimeSurvey group properties.
Args:
gid: The group ID.
properties: The properties to set.
Inputs: gid (required), properties (required).
set_language_propertiesC
Set LimeSurvey language properties.
Args:
lid: The language ID.
properties: The properties to set.
Inputs: lid (required), properties (required).
set_participant_propertiesC
Set LimeSurvey participant properties.
Args:
token: The participant token.
sid: The survey ID.
properties: The properties to set.
Inputs: token (required), sid (required), properties (required).
set_question_propertiesC
Set LimeSurvey question properties.
Args:
qid: The question ID.
properties: The properties to set.
Inputs: qid (required), properties (required).
set_quota_propertiesC
Set LimeSurvey quota properties.
Args:
id: The quota ID.
properties: The properties to set.
Inputs: id (required), properties (required).
set_survey_propertiesC
Set LimeSurvey survey properties.
Args:
sid: The survey ID.
properties: The properties to set.
Inputs: sid (required), properties (required).
update_responseC
Update a response in a LimeSurvey survey.
Args:
sid: The survey ID.
response_id: The response ID.
response: The updated response.
Inputs: sid (required), response_id (required), response (required).
upload_fileC
Upload a file to a LimeSurvey survey.
Args:
sid: The survey ID.
file_content: The file content (base64 encoded).
file_name: The file name.
Inputs: sid (required), file_content (required), file_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
B3.2/5.0
Scored across 35 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count3/5
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.
Completeness5/5
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.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
MCP server for the Seline Analytics API
MCP server for the Vulners.com API
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server to help manage a WHMCS installation.6258 npm24MIT
- AlicenseAqualityAmaintenanceMCP server for Huly (task tracker) integration61,022 npm64MIT
- AlicenseNot gradedqualityCmaintenancePublic MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.2MIT