Bring! MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRING_EMAIL | Yes | Email address of your Bring! account | |
| BRING_PASSWORD | Yes | Password of your Bring! account | |
| BRING_STORE_MAPPINGS | No | Path to the store mappings file (default: store_mappings.json in the project root) | store_mappings.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bring_get_listsA | Get all available Bring! shopping lists for the authenticated user. Returns list names and UUIDs. |
| bring_get_list_itemsA | Get all items from a specific Bring! shopping list. Returns items to purchase and recently purchased items. |
| bring_add_itemC | Add one or more items to a Bring! shopping list. Can add multiple items in a single call. |
| bring_complete_itemB | Mark an item as purchased/completed and remove it from the shopping list. |
| bring_remove_itemA | Completely remove an item from a shopping list (without marking as purchased). |
| bring_smart_addA | Smart-add items to Bring! shopping lists based on stored store preferences. Automatically routes each item to the correct store list (e.g. Aldi, Rewe) based on store_mappings.json. Items without a mapping are reported back. Use this instead of bring_add_item when you don't know which list an item belongs to. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools target distinct actions on distinct resources (lists vs items, add vs complete vs remove). The only potential overlap is bring_add_item vs bring_smart_add, but the smart_add description explicitly clarifies when to use each, so misselection risk is low.
All six tools follow a consistent bring_verb_noun pattern (bring_get_lists, bring_add_item, bring_complete_item, etc.). The prefix and verb style are uniform throughout, making the set predictable.
Six tools is well-scoped for a shopping-list integration: two read tools, two item mutations, and two add variants. Each tool earns its place with no redundant surface area.
Item lifecycle is well covered (get, add, complete, remove) and lists can be enumerated. Minor gaps exist—no create/delete list, no quantity/update-item operation—but core shopping workflows are achievable.