Cursor Software Sausage Recipe Finder Resource/Test whether a multi-agent workflow beats one agent
How to: Cursor Software Sausage Recipe Finder Test whether a multi-agent workflow beats one agent
Add Software Sausage Recipe Finder to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"recipes": {
"url": "https://softwaresausage.com/api/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Test whether a multi-agent workflow beats one agent is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
-
04
If it does not appear, check that Software Sausage Recipe Finder is connected and that you are looking at its resources 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 resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.