Install Fatsecret in Gemini CLI
What you need first
- Gemini CLI, installed.
- uv, which
gives the
uvxcommand the server starts with. - Your own values for
YOUR_FATSECRET_CONSUMER_KEY,YOUR_FATSECRET_CONSUMER_SECRET,YOUR_FATSECRET_MCP_SIGNING_KEY,YOUR_FATSECRET_MCP_USERS.
Steps
- Open
~/.gemini/settings.json, or create it. For one project only, use.gemini/settings.jsonin that project. - Add this block. If the file already has
mcpServers, add only the entry inside it.
{
"mcpServers": {
"fatsecret-mcp": {
"command": "uvx",
"args": ["fatsecret-mcp==0.1.0"],
"env": { "FATSECRET_CONSUMER_KEY": "YOUR_FATSECRET_CONSUMER_KEY", "FATSECRET_CONSUMER_SECRET": "YOUR_FATSECRET_CONSUMER_SECRET", "FATSECRET_MCP_SIGNING_KEY": "YOUR_FATSECRET_MCP_SIGNING_KEY", "FATSECRET_MCP_USERS": "YOUR_FATSECRET_MCP_USERS" }
}
}
} - Replace
YOUR_FATSECRET_CONSUMER_KEY,YOUR_FATSECRET_CONSUMER_SECRET,YOUR_FATSECRET_MCP_SIGNING_KEY,YOUR_FATSECRET_MCP_USERSwith your own values. - Save the file and restart Gemini CLI.
Check it worked
Ask Gemini CLI: List the tools of fatsecret-mcp.
If it does not start
- spawn uvx ENOENT
- uv is not on the PATH that Gemini CLI sees. Install it, or write the
full path of
uvxin the config. - The server starts, but its tools fail
- A
YOUR_…placeholder is still in the config, or its value is wrong. - Nothing changes after a restart
- The file is not valid JSON any more. Look for a missing comma where the block was added.