Connect any MCP client to Foodzilla
Foodzilla runs a standard MCP server at https://api.foodzilla.io/mcp with 61 tools. Any client that supports remote MCP servers and OAuth 2.1 sign-in should be able to use it. We've tested Claude and ChatGPT end to end. OpenClaw, Hermes Agent, Muse Code and Grok Bot each have their own setup page.
Integration Features
Use the agent you already have
If your agent supports remote MCP servers, it can create recipes, meal plan templates, forms and bookings in Foodzilla the same way Claude does.
Sign in without sharing a password
The client sends you to Foodzilla to sign in through OAuth 2.1 with PKCE. It receives a token, never your password.
Keep coach and client access apart
A coach token works on the coach's own account. A client token works on one client's diary and assigned plan. No token carries both.
How to Connect
Add a remote MCP server in your client and set the URL to https://api.foodzilla.io/mcp.
Let the client register itself. It finds Foodzilla's sign-in server through the protected resource metadata and uses dynamic client registration.
Sign in to Foodzilla. The client completes the OAuth 2.1 authorisation code flow with PKCE.
Check whether the consent page shows a coach or a client account, then connect.