An mcp server for groceries vendors
Groceries MCP server exists for a simple reason — assistants are far more useful when they can act on Groceries directly instead of describing what you should do. An mcp server for groceries vendors.
MCP Server for different Groceries vendor API, enabling searching groceries and cart update.
Once Groceries is connected, these are the calls the assistant has available:
Inputs — - items(list[CartItemScheam]): items to add to the cartReturns — Updated cartFeatures — The Features tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
You will need 3 environment variables: VENDOR_API_KEY, VENDOR_ACCOUNT_ID, YOUR_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Groceries's toolset — Inputs, Returns, Features — is a fair guide to whether it matches your workflow. It is maintained by o-b-one; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Inputs | - items(list[CartItemScheam]): items to add to the cart |
| Returns | Updated cart |
| Features | The Features tool exposed by this server. |
| Variable | Description | Required |
|---|---|---|
| VENDOR_API_KEY | Credential the server authenticates with. | Yes |
| VENDOR_ACCOUNT_ID | Configuration value read at startup. | Optional |
| YOUR_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.