bring-mcp
An MCP server that gives Claude (or any MCP client) access to your Bring! shopping lists.
- Lists: read, add (with quantities), update, check off and remove items. Names are matched against the Bring catalog, so items get their section and icon.
- Recipes: extract the ingredients of a recipe page with Bring's own parser, then add them in one go.
- Staples: keep a list of items you buy every week and add the missing ones, from Claude or from cron (no LLM involved).
- Runs locally for Claude Desktop (stdio), or remotely as a claude.ai custom connector (streamable HTTP + OAuth).
Unofficial project, not affiliated with or endorsed by Bring! Labs AG. It uses bring-api, an unofficial client of the Bring! API, which may change without notice.
Why this one
Other Bring! MCP servers map the API call by call (load list, save item, remove item...). This one gives the model tools shaped like the tasks you ask for:
- "Add what I need for this recipe": Bring's own recipe parser extracts the ingredients of a page in your list's language, and flags pantry items (salt, oil) so the model can ask before adding them.
- "Add 2 more litres of milk": an item already on the list gets its quantity merged instead of replaced, and names are matched against the Bring catalog (case, accents, simple plurals), so items land in the right section with their icon.
- Weekly staples: keep the list of things you always buy and add the missing ones in one call, or from cron without any LLM.
- Works in claude.ai on the web and on your phone, not only in Claude Desktop: a remote mode with OAuth, Docker and reverse-proxy configs, and a full deployment guide.
Tools
| Tool | What it does |
|---|---|
list_lists |
Names of your Bring lists. |
get_list |
Items to buy and recently bought items. |
add_items |
Add items with an optional spec ("6", "500 g", "organic"). An item already on the list gets its spec merged (1 L + 2 L). |
update_item |
Replace the spec of an item. |
complete_items |
Check items off (they move to "recently bought"). |
remove_items |
Remove items. |
fetch_recipe |
Ingredients of a recipe URL, in the list's language, with a pantry flag (salt, oil...). Adds nothing by itself. |
get_staples_list / set_staples_list |
Read or replace your staples. |
add_staples |
Add the staples that aren't on the list yet. |
Every tool takes an optional list (name, case-insensitive); without it, the
server uses BRING_DEFAULT_LIST, or your first list.
Prompts: add_recipe, clean_up_list, weekly_shopping.
Local setup (Claude Desktop)
Requirements: uv (or Python 3.12+) and a Bring! account that signs in with an email and password (if you use Google or Apple sign-in, set a password in the Bring app).
Add the server to claude_desktop_config.json. Open it from Claude Desktop →
Settings → Developer → Edit Config, or directly:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"bring": {
"command": "uvx",
"args": ["bring-mcp"],
"env": {
"BRING_EMAIL": "you@example.com",
"BRING_PASSWORD": "your-bring-password",
"BRING_DEFAULT_LIST": "Shopping"
}
}
}
}
Fully quit and restart Claude Desktop after editing the file.
Without uv: pip install bring-mcp, then use "command": "bring-mcp" (the full
path to that script if it isn't on your PATH) and no args.
Configuration
| Variable | Default | |
|---|---|---|
BRING_EMAIL |
(required) | Bring account email |
BRING_PASSWORD |
(required) | Bring account password |
BRING_DEFAULT_LIST |
(first list) | List used when a tool gets no list |
DATA_DIR |
~/.bring-mcp |
Where the SQLite file (staples, and OAuth tokens in remote mode) is kept |
The config file holds your Bring password: keep it readable by you only.
Remote setup (claude.ai connector)
python -m bring_mcp.server (or bring-mcp-remote) serves the same tools over
streamable HTTP, behind a single-user OAuth password page, for claude.ai on the
web and mobile. A Dockerfile and compose file are included, plus Apache and Caddy
configs that only let Anthropic's IP ranges reach /mcp.
See docs/deploy.md for the full guide (Docker, reverse proxy, claude.ai, weekly staples).
Security
- What's at stake. Your Bring password gives full access to your Bring account; this server can read and change your lists. It has no tool to delete lists, change account settings or invite people.
- Recipe pages are untrusted.
fetch_recipeasks Bring's servers to parse the page (this server never downloads it) and returns only ingredient names and quantities. The server instructions still tell the model not to follow text found there. Onlyhttp(s)URLs are accepted. - Inputs are bounded. Item names and specs are single-line and length-limited,
and a call handles at most 100 items.
remove_itemsandset_staples_listcarry the MCPdestructiveHint, so clients can ask before running them. - Remote mode:
- OAuth with a 20+ character password, a lockout after 5 failures, and tokens stored in SQLite.
- Only claude.ai's callback can be registered as redirect URI, and the number of clients is capped.
- The password page says which client asks and can't be framed by another site.
/mcpis restricted to Anthropic's outbound IPs by the reverse proxy.- The server refuses to listen on a public address, every tool call is logged, and the container is read-only and unprivileged.
- Remote mode, known limits:
- The lockout is global: anyone can make new logins wait 15 minutes by failing 5 times. Tokens already issued keep working.
- Anyone can add your server URL as a connector in their own claude.ai account and send you the resulting authorization link. If you type your password, their account gets access. Only type it right after clicking Connect yourself.
Keep .env and claude_desktop_config.json private. To report a vulnerability,
see SECURITY.md.
Limitations
- Catalog matching relies on bring-api's translation tables, read through private attributes; bring-api is pinned for that reason.
- Name matching ignores case, accents and a final
s/x; it doesn't know other plurals or synonyms. - Item photos, list sharing, notifications and loyalty cards are not supported.
Development
git clone https://github.com/vdeabreu/bring-mcp && cd bring-mcp
pip install -e ".[dev]"
pytest
ruff check .
Tests don't need a Bring account: they cover the tools against a fake list (merging, catalog names, list lookup, staples), input validation, re-login after an expired session, and the OAuth flow (redirect allowlist, client cap, lockout, security headers, startup checks).
License
Metadata
Release files for bring-mcp 0.1.0
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 |
|---|---|---|---|---|
| bring_mcp-0.1.0.tar.gz | 32.2 kB | With provenance | Details for bring_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bring_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bring_mcp-0.1.0-py3-none-any.whl |
Total release size: 53.4 kB
Release files / bring_mcp-0.1.0.tar.gz
| Download URL | bring_mcp-0.1.0.tar.gz |
|---|---|
| Size | 32.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69b337318dde190c4082f50b2df8f3a50f09f6c74128756bf1f2626ffa427505
|
|
BLAKE2b-256 checksum How to use checksums |
d42b37f626ca1061ac0bfa3e5e473d665e6b7d1901764538df46414c7b277e86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logRelease files / bring_mcp-0.1.0-py3-none-any.whl
| Download URL | bring_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bef69b36b64c0182838b608f13bb7ad51c81d79d5bd5590a25c6e1515bda598
|
|
BLAKE2b-256 checksum How to use checksums |
0074b2383d6c18b1ca96c6bd140430590d17c29d3140583811d162286609160e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logSecurity for bring-mcp 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bring_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logA 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.