FrancoLabs vs Simulatte
A side-by-side look at the FrancoLabs and Simulatte MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose FrancoLabs for research work over a hosted endpoint; choose Simulatte for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose FrancoLabs when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_question_types, list_templates, list_workspaces.
Choose Simulatte when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SIMULATTE_API_KEY. - You want tools like
simulatte_run_study, simulatte_get_results, simulatte_ask_insights.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 48/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | SIMULATTE_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
FrancoLabs tools 23
list_question_typesList question/block types and their settingslist_templatesList study templates, optionally by categorylist_workspacesList the workspaces (teams) you belong to and your role in eachlist_projectsList your projectsget_projectGet a single project by idcreate_projectCreate a new project (optionally in a specific workspace)list_studiesList studies (filter by status/project)get_studyGet a full study with blocks and settingscreate_studyCreate a study (auto-scaffolds welcome + thank-you)update_studyUpdate title, blocks, settings or projectset_study_statusLaunch / pause / resume / complete a studydelete_studyPermanently delete a study and its responses- +11 more on the listing page
Simulatte tools 7
simulatte_run_studyRun any of 26 research SKUs — concept testing, pricing, messaging, B2B committee, and moresimulatte_get_resultsRetrieve full structured results for a completed studysimulatte_ask_insightsAsk a natural-language question across your entire study history
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
FrancoLabs
{
"mcpServers": {
"francolabs": {
"url": "https://francolabs.vercel.app/mcp"
}
}
}
Simulatte
{
"mcpServers": {
"simulatte": {
"command": "npx",
"args": [
"-y",
"@simulatte-io/mcp-server"
],
"env": {
"SIMULATTE_API_KEY": "YOUR_SIMULATTE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
FrancoLabs is categorized under Research and uses a remote HTTP/SSE transport. Simulatte belongs to Research and uses a local stdio subprocess. Pick FrancoLabs for research work and Simulatte for research.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
FrancoLabs has no declared pricing — check the project's own site. Simulatte has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add francolabs and simulatte as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FrancoLabs has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Simulatte has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.