bring

This MCP server exposes the Bring! shopping list API through the Model Context Protocol, allowing MCP-enabled clients (such as Claude Desktop or MCP Inspector) to load lists, fetch and modify items, manage list users, and perform batch operations using standardized tools. The server authenticates automatically on first API call using the Bring! credentials supplied via environment variables or a .env file. Available tools include loading lists (loadLists), retrieving and manipulating items (getItems, getItemsDetails, saveItem, saveItemBatch, removeItem, moveToRecentList), handling images (saveItemImage, removeItemImage), managing users (getAllUsersFromList), retrieving settings (getUserSettings), obtaining the default list (getDefaultList), and loading translations/catalog data (loadTranslations, loadCatalog). It communicates over STDIO, making it compatible with Claude Desktop and the MCP Inspector for debugging and exploration of responses.

Prerequisites:

• Node.js and npm installed on your system
• Basic understanding of environment variables for credentials

Steps:

1. Clone the repository or download the project files.
2. Navigate into the project directory:

cd path/to/bring-mcp

3. Install dependencies:

npm install

4. Create a local environment file (optional if you prefer injecting env vars directly):

# .env
MAIL=your_email@example.com
PW=your_password

5. Build the project (if a build step is defined):

npm run build

6. Run the server directly (for testing):

node build/src/index.js

7. Alternatively, run via npx as recommended to auto-fetch the latest version:

npx -y bring-mcp@latest

Tips and considerations:

• Do not commit or share your .env file; use environment variables or a secure secret store.
• The server authenticates automatically on first use; ensure credentials are valid in Bring!'s account.
• If using Claude Desktop, the recommended configuration uses npx to fetch the latest bring-mcp package, ensuring compatibility with upcoming changes.
• You can also run the server locally with a prebuilt JS file (build/src/index.js) and point clients to that path using the manual local setup in the README.
• For debugging, MCP Inspector can be used to validate tool calls and responses; ensure npm run build has completed before testing.
• If you encounter network or API changes from Bring!, you may need to adjust the underlying bring-shopping package usage.