recipe-tools
Related Servers
Alternatives to recipe-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interactive selection of image regions from images and PDFs, with OCR support and automated export of selected regions as separate files.MIT
- AlicenseAqualityAmaintenanceFull-stack PDF intelligence MCP server for extracting, manipulating, annotating, converting, validating, and RAG-searching PDFs through a unified tool surface and React workbench.161MIT
- FlicenseNot gradedqualityBmaintenanceProvides secure PDF template analysis and layout extraction for AI assistants, enabling generation of styled HTML with automatic image generation.-
- AlicenseAqualityCmaintenanceConverts recipes from any source (web, YouTube, Instagram, etc.) into Thermomix format with guided cooking steps and uploads them to Cookidoo.4MIT
- AlicenseAqualityCmaintenanceConverts dense PDFs into soft, minimal, card-based HTML readers with preserved source text, rendered pages, and cropped tables/figures as images, all processed locally.32MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing recipes via a web UI and MCP tools, allowing retrieval and saving of recipe data through natural language.-
TDQS
Scored across 6 tools
Each tool has a distinct purpose: version info, working directory, prompt retrieval, image selection initiation, selection result retrieval, and HTML building. The paired select/get tools are clearly complementary with explicit descriptions. No two tools appear to do the same thing.
Most tools follow a verb_noun pattern, but the 'tool' suffix is applied inconsistently (e.g., get_server_version vs. get_working_directory_tool). The verbs are clear and predictable (get, select, build), but the naming style is slightly uneven.
With 6 tools, the set is well-scoped for a recipe-oriented MCP server. It covers both utility (version, working directory) and domain-specific operations (prompt, image selection, HTML generation) without being bloated or too sparse.
The core workflow is supported: get prompt, select image regions, fetch result, build HTML. Minor gaps exist (e.g., no explicit PDF-to-text tool, no recipe management), but the provided tools form a coherent pipeline for the intended use case.