create_paprika_recipeLABSCO SUMMARY
Recipes you talk about end up in the app you cook from.
The gap it closes is the copy-paste one: something worked out in conversation is written into Paprika itself, where your phone already syncs it. Recipe photos are marked as not yet covered.
What it is
A write path into Paprika 3 over its cloud sync: your existing recipes are readable as resources, and two tools create a new recipe or modify one you already keep.
What you get
- Your Paprika recipes exposed as readable resources
- A new recipe saved into your Paprika app
- An existing recipe modified in place
Requirements
Paprika 3 installed with cloud sync switched on, your Paprika username and password, and the binary on your PATH — prebuilt releases exist for macOS through Homebrew, and as archives for Linux and Windows.
Setup effort
Follow the published steps — brew tap soggycactus/tap
USE CASES
Keeping a recipe you just worked out
The version you settled on goes into the app in one call, instead of being retyped later from a scrollback.
Fixing a recipe after you have cooked it
Adjust the timings or quantities that were wrong while you still remember what went wrong.
Scaling or substituting without retyping
Describe the change and the stored recipe is rewritten, rather than duplicated by hand.
Getting a recipe onto your phone before you shop
Saving through cloud sync means it is on the device you take to the shop, not in a chat you have to find again.
2 tools
Listed in project docs. Your client may show a different list.
update_paprika_recipeBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
brew tap soggycactus/tap
brew install paprika-3-mcpMCP Clients
Any MCP client
{
"mcpServers": {
"paprika-3": {
"command": "paprika-3-mcp",
"args": [
"--username",
"<YOUR_PAPRIKA_USERNAME>",
"--password",
"<YOUR_PAPRIKA_PASSWORD>"
]
}
}
}