Cursor LiquiLens — the Failure Radar Prompt/stress_evidence_pack
How to: Cursor LiquiLens — the Failure Radar stress_evidence_pack
Add LiquiLens — the Failure Radar to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"liquilens": {
"url": "https://api.liquilens.in/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
stress_evidence_pack is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Cursor will not call it for you.
-
04
If it does not appear, check that LiquiLens — the Failure Radar is connected and that you are looking at its prompts rather than its tools.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.