Server and connection
Use the server address shown below with an MCP client that supports Streamable HTTP and OAuth. The older address remains available only for backward compatibility.
Add the server in your MCP client. The client opens BARFLAB sign-in and consent. Review the requested permissions before allowing access. An API access token is not an MCP credential and must not be pasted into an MCP client.
Available tools
Tools cover pets, saved diets, measurements, personal supplements, product lookup, files, and unsaved diet proposals. Every operation follows the permissions granted during OAuth.
Diet tools can generate, validate, save, and read one shared batch for multiple compatible pets. Group-aware clients explicitly include shared batches in diet lists and reads, and a generated shared proposal can be saved unchanged.
Try it
After connecting, ask the client to list your pets. It should return only pets owned by the connected account. Generating a proposal does not save a diet.
Disconnect and troubleshoot
Remove the connection in BARFLAB connected-app settings to block further calls and token renewal. If a client does not support Streamable HTTP or OAuth, it cannot connect yet. Reconnect through the consent flow when a connection expires or is denied.