Fatsecret MCP vs Wellness Nourish

In-depth architectural comparison of the Fatsecret MCP and Wellness Nourish MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Fatsecret MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Fatsecret MCP Details

Choose Wellness Nourish when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Wellness Nourish Details

Feature & Specification Comparison

Specification	Fatsecret MCP Developer Tools	Wellness Nourish Developer Tools
Summary	MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial)	Local-first nutrition MCP for AI agents: food, barcode, photo, intake, hydration, goals.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "fatsecret-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fatsecret-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "wellness-nourish": {
      "command": "npx",
      "args": [
        "-y",
        "delx-wellness-hermes"
      ]
    }
  }
}

Related MCP Server Comparisons