Food Logger MCP

ai.sig.foodlogPublished by foodlog.sig.aiOfficial publisherv1.1.0Updated Oct 24, 2026

Food logging, nutrition summaries, and meal photo calorie and macro estimates.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server for logging meals and getting nutrition summaries, including calorie and macro estimates from meal photos.

What you can do
  • Log meals and keep a food diary through the assistant
  • Retrieve nutrition summaries of logged intake
  • Estimate calories and macros from meal photos
  • Requires a bearer token tied to a Food Logger account
When to use it
Useful when you want an assistant to keep a food diary, tally daily calories and macros, or estimate nutrition from a photo of a meal without leaving the chat.
Requirements
Remote streamable HTTP endpoint at foodlog.sig.ai; no local install. A Food Logger account and a bearer token sent in the Authorization header, obtained from the provider's account page. New users reportedly get 5 trial photo-analysis credits.
Before you install
The Authorization bearer token is a secret; keep it out of shared logs and transcripts. Meal photos and food data are sent to the provider's service. Photo analysis may be limited by trial credits or paid usage, so check pricing before relying on it.

Installation

In SourceWeft

  1. Open Food Logger MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.sig.foodlog%2Ffood-logger/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "food-logger": {
      "type": "http",
      "url": "https://foodlog.sig.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.