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 分