Paprika MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAPRIKA_EMAIL | No | Your Paprika account email address | |
| PAPRIKA_PASSWORD | No | Your Paprika account password | |
| PAPRIKA_USER_AGENT | No | User-Agent string for Paprika API requests (optional, auto-detected if Paprika for Mac is installed) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recipesA | Search recipes by text across title, ingredients, categories, directions, or notes. Returns recipe IDs, titles, and context for each match. Use an empty query ('') to get all recipes. Results are paginated and sorted alphabetically. Only non-trashed recipes are included. |
| read_recipeA | Read full recipe data by ID or exact title. Returns all recipe fields including categories, times, ingredients, directions, etc. |
| update_recipeA | Update recipe fields using find/replace. This is a DANGEROUS operation that requires user confirmation. Can update any text field in a recipe. |
| format_fractionA | Format a fraction string to unicode fraction characters. Converts simple fractions like '1/4' to '¼' or complex ones like '31/200' to '³¹⁄₂₀₀'. Handles already-formatted unicode fractions and strips whitespace. This tool does not require server connectivity and can be used for testing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| user_preferences | Load user preferences and high-level context from ~/.paprika-mcp/prompt.md. This can include dietary restrictions, favorite ingredients, or other helpful context. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: format_fraction handles text formatting, read_recipe retrieves specific recipes, search_recipes finds recipes via queries, and update_recipe modifies recipes. The descriptions clearly differentiate between data retrieval (read/search) and operations (format/update).
All tools follow a consistent verb_noun pattern (format_fraction, read_recipe, search_recipes, update_recipe) with no deviations. The naming is predictable and readable, using snake_case uniformly across all tools.
Four tools are reasonable for a recipe management server, covering core operations like reading, searching, updating, and a utility for formatting. It might benefit from additional tools for creating or deleting recipes, but the current set is well-scoped for basic functionality.
The tools cover key operations (read, search, update) and include a useful formatting utility, but there are notable gaps: no create_recipe or delete_recipe tools, which limits full CRUD lifecycle coverage. Agents can work around this for read/update tasks but cannot handle recipe creation or removal.