MCP Server for Bring! Shopping

Created By
florianwittkampa year ago
MCP Server for Bring! Shopping
Overview

What is MCP Server for Bring! Shopping?

MCP Server for Bring! Shopping is a local Model Context Protocol (MCP) server implemented in TypeScript that allows applications to interact with Bring! shopping lists using standardized MCP tools.

How to use MCP Server for Bring! Shopping?

To use the MCP server, configure it in your Claude Desktop by adding the provided JSON configuration to your claude_desktop_config.json file, ensuring you include your Bring! credentials.

Key features of MCP Server for Bring! Shopping?

  • Automatic authentication on first API call.
  • Exposes Bring! API functions as MCP tools, including loading shopping lists, modifying items, and managing list users.
  • Supports batch operations for efficiency.
  • Communicates via STDIO for integration with Claude Desktop or MCP Inspector.

Use cases of MCP Server for Bring! Shopping?

  1. Integrating Bring! shopping lists with desktop applications.
  2. Automating shopping list management tasks.
  3. Enhancing user experience with seamless API interactions.

FAQ from MCP Server for Bring! Shopping?

  • Is this project affiliated with Bring! Labs AG?

No, this is a personal project and uses an unofficial Bring! API.

  • How do I set up the server?

Follow the setup instructions in the documentation, including cloning the repo and configuring your environment variables.

  • What happens if the unofficial API changes?

The server may stop functioning if the unofficial API changes or is blocked.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
florianwittkamp
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago