Schema | MyFitnessPal MCP Server

MyFitnessPal MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_HOST`	No	Bind address for HTTP mode (default 127.0.0.1, 0.0.0.0 in Docker)	127.0.0.1
`MCP_PORT`	No	Port for HTTP mode (default 8000)	8000
`MCP_TRANSPORT`	No	Transport: stdio or streamable-http (default stdio, streamable-http in Docker)	stdio
`MCP_RESOURCE_URL`	No	Exact public URL clients use (e.g. https://mfp.example.com); required with passcode
`MFP_COOKIES_FILE`	No	Path to JSON cookies file in format {"cookies": {name: value}} or plain {name: value}
`MCP_ALLOWED_HOSTS`	No	Comma-separated allowed Host headers for reverse proxy (optional, enables DNS-rebinding protection)
`MCP_OAUTH_PASSCODE`	No	Shared passcode for OAuth login page (omit for unauthenticated LAN-only use)
`MFP_FIREFOX_PROFILE_DIR`	No	Path to Firefox profile directory containing cookies.sqlite with a logged-in MFP session (default /profile in Docker)

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delize/myfitness-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server