Groceries

Provides grocery search and cart management via a vendor API using MCP, enabling item lookup and automatic cart updates.

javascript

3

GitHub Stars

javascript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "o-b-one-groceries-mcp": {
      "command": "uv",
      "args": [
        "run",
        "mcp-groceries-server",
        "--vendor",
        "vendorName"
      ],
      "env": {
        "VENDOR_API_KEY": "<YOUR_API_TOKEN>",
        "VENDOR_ACCOUNT_ID": "<VENDOR_ACCOUNT_ID>"
      }
    }
  }
}

This MCP server enables you to search groceries via a vendor API and automatically create and update a cart by adding items you specify. It streamlines shopping workflows by providing a simple programmatic interface to look up items and place them into a cart.

How to use

To use this MCP server with a client, you will run the server as a stdio process and interact with two main capabilities: search for groceries and add items to the cart. Start by configuring your environment with the required vendor credentials, then provide the item list you want to add to the cart. Use the search feature to find matching items before adding them to ensure you select the correct product variants.

How to install

Prerequisites: Ensure you have a runtime tool available to start the MCP server (the guide uses UV as the runner). You should also prepare your environment variables for the vendor API.

Prepare environment variables for vendor access. You will need the following values: VENDOR_API_KEY and VENDOR_ACCOUNT_ID. These are used to authenticate with the vendor API.
Create or update your environment configuration file as needed. The setup flow typically includes an environment template that you adapt to your environment.
Start the MCP server using the provided start command and vendor configuration. The example startup command uses UV to run the groceries MCP server and passes the vendor name as a parameter.

Additional content

Configuration details: Use the following explicit runtime command to start the server, including the vendor context: uv run mcp-groceries-server --vendor vendorName. Set the environment variables VENDOR_API_KEY and VENDOR_ACCOUNT_ID with your vendor credentials. You can also supply these variables directly in your shell or within your process manager.

Usage notes: Local development can reuse the same command pattern. When you deploy, ensure the vendor credentials are securely managed and not committed to shared code repositories.

Security and notes

Treat vendor credentials as secrets. Use a secure environment management approach (e.g., secret stores or protected environment files). Never expose VENDOR_API_KEY and VENDOR_ACCOUNT_ID in client-side code or public repositories.

Troubleshooting and tips

If the server fails to start, verify that you are providing the required environment variables and that the vendorName parameter is valid for your setup. Check that the runtime tool (UV) is installed and accessible in your environment. Ensure network access to the vendor API is available if you encounter lookup or cart update failures.

Available tools

add_items_to_cart

Add groceries to the basket by supplying a list of items; returns the updated cart.

search

Lookup for an item in the vendor catalog by providing a search term; returns a list of matching items.