Connect an MCP server
If you already run an MCP server for Claude, Cursor or anything else, that is the one.
On this machine (stdio)
Section titled “On this machine (stdio)”RigorRun runs the command directly rather than through a shell, so nothing you type is interpreted as shell syntax.
- Command — just the program, no arguments. For example
npx. - Arguments — one per line; everything you would type after the command.
Somewhere else (streamable HTTP)
Section titled “Somewhere else (streamable HTTP)”A private address is fine. RigorRun runs on your machine, so anything this machine can reach, it can reach.
Authentication is either a credential you already hold, sent as a header, or OAuth. Signing in opens your browser once; the tokens go into this machine’s credential store with everything else, and never into the project file. A second connection opens no browser.
Two questions RigorRun has to ask
Section titled “Two questions RigorRun has to ask”Neither can be worked out from the outside.
Which tools only look. Your server can annotate a tool readOnlyHint: true, and RigorRun shows
you when it does — labelled as the server’s claim. It will not enforce against it. An annotation
is a claim by the software being tested, and treating it as a permission is exactly the failure
rigorrun verify exists to find.
Which tools check what happened. After your agent finishes, RigorRun calls these to see what really changed. Without at least one, there is no verdict worth having, and RigorRun says so rather than producing one.
A reset
Section titled “A reset”If one tool puts the system back, nominate it. RigorRun calls it before every case so each starts
from the same place. Note that a nominated reset gives DECLARED isolation,
not RESET — RigorRun has not run it twice and compared.
When the session drops
Section titled “When the session drops”The stdio connector is a child process, so it does not survive a runner restart. The project shows not connected with a Reconnect button; nothing is lost.