LabscoMCP early access ↗
edgarrmondragonMCP SERVER

LimeSurvey

A minimal bridge to a LimeSurvey instance's RemoteControl API.

by edgarrmondragon ↗Forms & SurveysCommunity

LABSCO SUMMARY

It authenticates as a person, not as a scoped app.

The configuration takes your LimeSurvey username and password, which means whatever that account can do in the admin UI is what the connection can do. Use a dedicated account with only the survey permissions you intend to expose rather than an administrator login, and keep the credentials in the client's environment block rather than a file in the repo.

What it is

A small Python server that connects an MCP client to a LimeSurvey instance, so surveys and their responses can be managed from the assistant rather than the admin UI. It is deliberately thin — a direct wrapper over the LimeSurvey remote API with a three-variable configuration.

What you get

  • Access to your LimeSurvey surveys and their responses through a running MCP client
  • Configuration is three variables and nothing else — no per-survey setup
  • It talks to whichever instance you point it at, hosted or self-run, through that instance's RemoteControl endpoint
  • It runs locally over stdio, so survey data goes between your machine and your own LimeSurvey server

Requirements

A LimeSurvey instance with the RemoteControl API enabled, plus an account on it. Three environment variables: LIMESURVEY_URL pointing at the instance's /admin/remotecontrol path, LIMESURVEY_USERNAME and LIMESURVEY_PASSWORD. Published as mcp-limesurvey version 0.0.1; the documented client entry runs uv with --directory pointing at the checkout, followed by run and main.py, so uv and a local checkout are what you need.

Setup effort

Build from source — git clone https://github.com/edgarrmondragon/limesurvey-mcp.git

See installation options