Foodzilla
Foodzilla AutopilotNot tested by Foodzilla yet. Claude and ChatGPT are the two we've tested end to end.

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

1

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.

2

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.

3

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

1

Add a remote MCP server in your client and set the URL to https://api.foodzilla.io/mcp.

2

Let the client register itself. It finds Foodzilla's sign-in server through the protected resource metadata and uses dynamic client registration.

3

Sign in to Foodzilla. The client completes the OAuth 2.1 authorisation code flow with PKCE.

4

Check whether the consent page shows a coach or a client account, then connect.

What You Get with Foodzilla

One endpoint with 61 tools over standard Streamable HTTP and JSON-RPC 2.0.
No API key to copy. Clients register themselves and sign in with OAuth.
Nutrition data from Foodzilla's food database, not from the model.
Included on Professional and higher plans at no extra cost.

Frequently Asked Questions

Connect Other AI Agents to Foodzilla over MCP