This is an MCP server for LimeSurvey. It is a simple server that allows you to manage your LimeSurvey surveys and responses.
This is an MCP server for LimeSurvey. It is a simple server that allows you to manage your LimeSurvey surveys and responses. The limesurvey mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
LIMESURVEY_URL — The URL of your LimeSurvey instance, e.g. https://myinstance.limequery.com/admin/remotecontrolLIMESURVEY_USERNAME — Your LimeSurvey usernameLIMESURVEY_PASSWORD — Your LimeSurvey passwordSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 3 environment variables: LIMESURVEY_URL, LIMESURVEY_USERNAME, LIMESURVEY_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Limesurvey MCP's toolset — LIMESURVEY_URL, LIMESURVEY_USERNAME, LIMESURVEY_PASSWORD — is a fair guide to whether it matches your workflow. It is maintained by edgarrmondragon; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| LIMESURVEY_URL | The URL of your LimeSurvey instance, e.g. https://myinstance.limequery.com/admin/remotecontrol |
| LIMESURVEY_USERNAME | Your LimeSurvey username |
| LIMESURVEY_PASSWORD | Your LimeSurvey password |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LIMESURVEY_URL | Endpoint or connection string the server talks to. | Yes |
| LIMESURVEY_USERNAME | Configuration value read at startup. | Optional |
| LIMESURVEY_PASSWORD | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.