Bring MCP Server

Created By
DavideArenaa year ago
Overview

What is Bring MCP Server?

Bring MCP Server is a Model Context Protocol (MCP) server that integrates with the Bring Shopping Lists API, enabling AI assistants to manage shopping lists through natural language.

How to use Bring MCP Server?

To use Bring MCP Server, clone the repository, install dependencies, configure your Bring account details in a .env file, and start the server. Connect your AI assistant, like Claude for Desktop, to interact with your shopping lists.

Key features of Bring MCP Server?

  • Implements the Model Context Protocol for seamless AI integration.
  • Supports stdio transport for compatibility with MCP clients.
  • Full integration with the Bring Shopping List API, allowing users to manage their shopping lists effectively.

Use cases of Bring MCP Server?

  1. Managing shopping lists through voice commands.
  2. Integrating with AI assistants for personalized shopping experiences.
  3. Automating grocery list management for households.

FAQ from Bring MCP Server?

  • What is the MCP protocol?

The Model Context Protocol is a standardized protocol that allows AI assistants to communicate with various services.

  • Is the Bring API officially supported?

No, the project uses unofficial Bring APIs that may change without notice.

  • What are the prerequisites for using this server?

You need a Bring account and an API key to use the server.

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

Recommend Servers

View All
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