Bring Photo MCP server

Bring Photo MCP v1

English | Deutsch

Turn product photos into Bring! shopping-list items.

Show your AI agent a package, label, or product photo and say: “Add this to my shopping list.” Bring Photo MCP lets the agent identify the product, match it with the Bring! catalog, select the right category and icon, attach the photo, and add the verified result to your Bring! list.

It also provides the usual list operations—searching, adding, checking, moving, copying, and removing items—but the photo-first workflow is the point: less typing, fewer ambiguous product names, and the original product image directly on the list.

Bring Photo MCP is a local, agent-neutral TypeScript MCP server. The executable stdio entrypoint starts only with locally validated environment variables; this repository contains no Hermes or client runtime configuration.

Installation

Requirements: Node.js 20+ and npm.

npm install
npm run typecheck
npm run lint
npm test
npm run build

The official MCP TypeScript SDK (@modelcontextprotocol/sdk) is used. npm start builds the project and starts src/index.ts as a stdio server. Startup validates the configuration and authenticates with Bring only afterwards; this repository intentionally contains no Hermes or client runtime configuration.

Distributable artifacts

The package is prepared for public npm publication, constrained by an explicit files allowlist, and includes a bring-photo-mcp stdio binary entrypoint. The public thin-skill guidance is in SKILL.md; tested client templates are in docs/MCP-CLIENT-CONFIGURATION.md. Migration and rollback without runtime cutover are specified in docs/MIGRATION-ROLLBACK.md.

Configuration

Never commit .env with real values. The configuration model expects:

• BRING_ENV=test|prod
• BRINGEMAIL, BRINGPASSWORD
• BRINGDEFAULTLIST
• BRINGALLOWEDLISTS (comma-separated)
• BRING_LOCALE (default de-DE)
• BRINGTESTITEM_PREFIX (default MCP-TEST-)
• optional BRINGTESTSECOND_LIST exclusively for the multi-list E2E

src/config.ts validates the values. In PROD, the service accepts only allowlisted lists; the production runtime must additionally point to a pinned release tag. TEST uses a dedicated allowlisted list and temporary prefixed test items only.

Opt-in live E2E

npm run test:e2e is deliberately not part of npm test and was not run here. It starts only with a fully configured environment and rejects anything other than BRINGENV=test. BRINGALLOWEDLISTS must contain exactly BRINGDEFAULTLIST; with BRINGTESTSECONDLIST, it must contain exactly both named configured TEST lists. A non-empty BRINGTESTITEM_PREFIX is required.

The harness creates two synthetic PNG files in the temporary directory, verifies add/read-back as well as photo replace/remove, and removes all of its own prefixed items in finally, followed by an absence check. Copy, move, and multi-list operations run only with an explicit BRINGTESTSECOND_LIST; without it, the harness reports an honest skip.

Architecture

Shortened. The full README is on GitHub.