Cronometer MCP

io.github.atticoos由 GitHub 帳號 atticoos 發布v0.3.0更新於 Nov 7, 2026

Review nutrition, log meals, and manage foods and recipes in your Cronometer account.

已驗證Streamable HTTP可網頁執行位置與生活資料與分析

概覽

AI 產生的概覽

非官方遠端 MCP 伺服器，讓助理讀取並修改你的 Cronometer 飲食日記、營養總量、食譜、斷食與身體測量資料。

可以做什麼
  • 讀取飲食日記與每日營養總量，並查看連線狀態
  • 搜尋 Cronometer 食物資料庫，查看食物詳情與份量
  • 新增、刪除、複製飲食紀錄，標記某天完成或未完成
  • 依營養資訊或食材建立自訂食物與食譜
  • 取得巨量營養目標、斷食歷史與統計、身體測量趨勢
  • 依日期範圍匯出每日營養摘要、食物份量、運動、身體測量與備註
適用情境
適合在 Cronometer 記錄飲食與健康資料，並想透過對話詢問今日熱量或營養、記錄餐點、建立食譜，或回顧體重與斷食趨勢的使用者。
執行需求
需要 Cronometer 帳號，以及支援遠端 HTTP 伺服器與 OAuth 驗證的 MCP 用戶端。在用戶端的 MCP 設定中新增遠端伺服器網址，並以 Cronometer 使用者名稱、密碼及可能的一次性驗證碼完成瀏覽器登入。不需要 API 金鑰或環境變數。
安裝前請注意
登入時會把 Cronometer 憑證交給伺服器營運方，請只使用你信任的營運方。此連線授予讀寫權限：工具可刪除飲食紀錄、建立食物與食譜、複製某天紀錄並標記完成狀態，而名為 cronometer:read 的 OAuth 範圍並不強制唯讀，目前也沒有唯讀模式。回傳的資料會交給你的助理，受該用戶端的資料處理政策約束。匯出每次最多 31 天、每天約 10 次，且依賴 Cronometer 私有 API，可能隨時變動。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Cronometer MCP，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.atticoos%2Fcronometer-mcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "cronometer": {
      "type": "http",
      "url": "https://mcp.cronometer-mcp.dev/mcp"
    }
  }
}

README

Cronometer MCP

Connect your AI assistant to Cronometer to review your nutrition, log meals, and explore your tracking history in conversation.

Cronometer MCP is an unofficial Model Context Protocol (MCP) server that gives compatible assistants access to your Cronometer account. It supports reading your data and making changes to your food diary, custom foods, and recipes.

What you can do

  • Review your nutrition: see your food diary, calories consumed and remaining, and tracked macro and micronutrient totals.
  • Log and manage meals: search Cronometer's food database, add or delete food entries, copy the previous day's entries, and mark days complete or incomplete.
  • Create foods and recipes: save a custom food from nutrition information or build a recipe from ingredients.
  • Explore your history: retrieve macro targets, fasting history and statistics, and biometric trends such as weight or body fat.
  • Retrieve exports: access daily nutrition summaries, food servings, exercises, biometrics, and notes for a date range.

Connect your assistant

You need a Cronometer account and an MCP client that supports remote HTTP servers with OAuth authentication.

  1. Add a remote MCP server in your assistant's MCP connection settings.

  2. Enter the server URL:

    text
    https://mcp.cronometer-mcp.dev/mcp

  3. Review the requested read and write access, then complete the browser sign-in flow with your Cronometer username, password, and one-time code if required.

  4. Return to your assistant and ask it to check the connection or retrieve today's food diary.

Connection settings and tool permissions vary by client. If you need to run your own server, follow the self-hosting guide.

About the npm package: npx cronometer-mcp currently runs a placeholder server with only a status tool. Use the remote server described here for Cronometer data tools. See the package README for its current status.

Try asking

  • “What have I eaten today, and how many calories do I have left?”
  • “Show my protein, fiber, and sodium totals for yesterday.”
  • “Find cooked brown rice and log 150 grams for lunch today.”
  • “Create a recipe from 200 grams of chicken breast and 150 grams of cooked rice.”
  • “How has my weight changed over the last 30 days?”
  • “Summarize my fasting history for the past month.”
  • “Retrieve my daily nutrition summaries for the last seven days.”

Available answers depend on what you track in Cronometer. Your assistant can use food search and serving details to identify foods before logging them.

Account access and privacy

During sign-in, the MCP server receives your Cronometer credentials and exchanges them with Cronometer for sessions. Your password and one-time code are not stored or included in MCP tokens; upstream sessions are stored in encrypted OAuth grant properties. Use a server operator you trust with your account access.

Data returned by tools becomes available to your assistant and is subject to that client's data handling policies. Write tools can change your Cronometer account, including deleting existing food entries, creating custom foods and recipes, copying diary entries, and marking days complete or incomplete. Review your client's tool permissions before allowing changes.

The sign-in screen requests read and write access. The OAuth scope is still named cronometer:read for compatibility with existing clients. Despite that legacy name, it does not enforce read-only access: an authorized connection has access to all the tools listed below. There is currently no read-only connection mode. You can revoke the MCP connection at any time.

If a Cronometer session expires, follow the sign-in prompt from your MCP client, then retry the tool. The server discards your password after sign-in.

Available tools

AreaTools
Connectionconnection_status
Food diaryget_food_log, add_food_entry, remove_food_entry, copy_day, mark_day_complete
Nutrition and food searchget_daily_nutrition, search_foods, get_food_details
Custom foods and recipesadd_custom_food, add_recipe
Targetsget_macro_targets
Fastingget_fasting_history, get_fasting_stats
Biometricslist_biometrics, get_biometrics
Data exportsget_cronometer_data

Limits and troubleshooting

  • Expired connection: if your client does not show a sign-in prompt, reconnect the MCP server in your client and sign in again.
  • Missing nutrients: daily nutrition totals include nutrients with targets set in your Cronometer account.
  • Dates: tools accept YYYY-MM-DD dates. Diary tools with an optional date default to today in your account's timezone.
  • Copying a day: copy_day adds the previous day's entries to the destination date and keeps existing entries. Repeating it can create duplicates.
  • Export limits: each export covers at most 31 inclusive days and returns up to 1,000 rows. Shorten the range if a result is truncated. Exports count toward Cronometer's limited daily export allowance (roughly 10 per day); the mobile data tools do not use that allowance.
  • Service changes: this project uses Cronometer's private mobile and web APIs. Changes to those APIs may temporarily break features.

Development and self-hosting

See the development guide for local setup, Cloudflare deployment, authentication details, secrets, and CI configuration. The mobile API contract is maintained in specs/cronometer-mobile.yaml.

Acknowledgments

The mobile API integration is a TypeScript port of rwestergren/cronometer-api-mcp (MIT). The CSV export protocol was independently implemented using jrmycanady/gocronometer as a reference. See the development guide for implementation and licensing notes.

License

MIT. Notices for ported third-party code are in THIRD_PARTY_NOTICES.

來源：README.md，提交 75e5b57

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v0.3.0最新Nov 7, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分