Schema | HelloFresh MCP

HelloFresh MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HELLOFRESH_DEBUG`	No	Log the bridge's role and lifecycle to stderr.	off
`MCP_CONFIRM_MODE`	No	What a write does on a client that cannot show a confirmation prompt. One of: ask-user (the model must show you the preview and get your approval in chat before reusing the token), auto (the model may use the token itself after seeing the preview), refuse (writes are refused; an unrecognised value is treated as refuse).	ask-user
`HELLOFRESH_WS_PORT`	No	The fetchproxy bridge port. The whole fetchproxy fleet and ContextMint Bridge share 37149. Override it only for local testing, or when a host injects a per-registration port.	37149
`HELLOFRESH_PROFILES`	No	The meal-planner profiles as an inline JSON array (wins over the file).
`MCP_CONFIRM_ELICITATION`	No	off never shows a confirmation prompt, so every client takes the MCP_CONFIRM_MODE path. Use it for clients that declare prompts but never render them.	on
`HELLOFRESH_PROFILES_FILE`	No	A JSON file of planner profiles, read when it exists. With neither this nor HELLOFRESH_PROFILES set, the built-in couple and family profiles apply.	~/.config/hellofresh-mcp/profiles.json

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo recent community issues