MCP_FILE_PATH is the whole story on the file side: the tool works inside that directory and nowhere else, so pointing it at a scratch folder is the difference between convenience and risk. The image check and the recipe lookup run against LuckyCola's platform and draw on your account's quota.
A Node MCP server over LuckyCola's open platform. Running it returns three tools: a compliance check on an image URL, a recipe lookup by dish name, and a file operation tool scoped to a single directory you set.
- An online image checked for compliance, returning a safety status, a safety score and the detection detail
- A dish's recipe returned with introduction, steps, ingredients, cautions and timing
- Files under your nominated directory deleted, renamed, read and written
- Image compression, handled by the same file operation tool
Node.js v21.0.0 or above, a LuckyCola account for LUCKYCOLA_OPEN_KEY and LUCKYCOLA_OPEN_UID from the user centre, and MCP_FILE_PATH set to the directory the file tools may touch.
One command plus a key — npx -y luckycola-mcp, then supply credentials
