Digest
Local-first nutrition tracking that runs inside Claude. You log food by chatting. Your data lives in a SQLite file on your machine — no account, no cloud, no signup. A color-coded dashboard shows five numbers at a glance: calories, protein, fiber, carbs, fat. Protein and fiber are targets. Carbs and fat are limits. That's the whole product.
Note: This is a pre-alpha release (
0.0.1) reserving the package name while development continues. The core functionality works, but features are still being added. Watch the repo for the 0.1.0 release.
What Digest does
- Search foods across USDA FoodData Central (380K+) and Open Food Facts (4M+ branded products)
- Barcode lookup (UPC/EAN)
- Log meals via natural conversation — calories, protein, carbs, fat, fiber
- Track goals as targets (protein, fiber) or limits (carbs, fat)
- Visual dashboard — color-coded progress bars with a calorie ring, updates in place
- Edit and delete entries with natural language
- CSV export so your data is never locked in
What Digest doesn't do, by design
- No meal plans or recipe suggestions
- No grocery lists
- No social feed, streaks, or gamification
- No coaching, nudges, or "helpful" reminders
- No account, login, or cloud sync
- No ads, ever
Label photos work. Snap a picture of any nutrition facts panel, paste it into chat, and Claude reads the numbers and logs them. No special tool needed.
Data location
All data lives in ~/.digest/digest.db — a single SQLite file. Delete it and it's gone. Export to CSV anytime. Query it directly with sqlite3 if you want.
Install
pip install digest-mcp
Configure (Claude Desktop)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"digest": {
"command": "digest-mcp",
"env": {
"USDA_API_KEY": "DEMO_KEY"
}
}
}
}
The DEMO_KEY works for light personal use (~30 requests/hour). For higher limits, get a free key at fdc.nal.usda.gov/api-key-signup.
Restart Claude Desktop, and Digest's tools become available in any chat.
License
MIT. Do whatever you want with it.
Author
Mya — mya@twobitcircus.org
Metadata
Release files for digest-mcp 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| digest_mcp-0.0.1.tar.gz | 15.8 kB | Without provenance | Details for digest_mcp-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| digest_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for digest_mcp-0.0.1-py3-none-any.whl |
Total release size: 31.9 kB
Release files / digest_mcp-0.0.1.tar.gz
| Download URL | digest_mcp-0.0.1.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aab1d34d902ef0e3f3904eb8377c3b31c5aa393daa34c9d5b162ede225a4fd4c
|
|
BLAKE2b-256 checksum How to use checksums |
e4d68dc026fdc6e05966fb90e8bd1d44a3433c2ea59917de43ff58afb8feb015
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / digest_mcp-0.0.1-py3-none-any.whl
| Download URL | digest_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4933e111a1803ded84ec077619f1f8dce1e258fd004fe38900cfb27256152291
|
|
BLAKE2b-256 checksum How to use checksums |
6c5b4ab8c532961c512efbde047a22a10bd1600c744c7e29c9a72eef3c56ba08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for digest-mcp 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.