Skip to main content
Glama

kassalapp-mcp

Grocery prices per chain from Kassalapp, by voice: an MCP server and claude-voice plugin.

It answers two questions, by voice: what a grocery costs at each chain, and where it is cheapest. Every answer says how old the price is. It only reads prices and never buys anything.

Kassalapp has no current prices from Kiwi, REMA 1000 or Coop, and the plugin says so rather than give an old price as if it were new. Prices are per chain, not per shop. Price data comes from Kassalapp.

Try it on made-up prices, with no key and nothing sent:

$ kassalapp-mcp price "fjellmelk lett 1 l" --chain Meny --simulate
Simulated: Fjellmelk lett 1 l costs 26.90 at Meny, checked today. Kassalapp's prices are per chain, not per shop.
$ kassalapp-mcp price fjellmelk --simulate
Simulated: Which one: Fjellmelk lett 1 l, Fjellmelk hel 1 l or Fjellmelk skummet 1 l?

For real prices, make your own free key at kassal.app/profil/api, and save it in ~/.config/kassalapp-mcp/key, readable by you alone. Without it, every answer says the plugin is not set up, and nothing is sent.

A voice session starts it as an MCP server over stdio:

$ kassalapp-mcp serve --help
usage: kassalapp-mcp serve [-h] [--simulate] [--key-file KEY_FILE] [--state-dir STATE_DIR]

options:
  -h, --help            show this help message and exit
  --simulate            answer from made-up prices
  --key-file KEY_FILE   the Kassalapp key (default ~/.config/kassalapp-mcp/key)
  --state-dir STATE_DIR
                        the cache and call counts (default ~/.local/state/kassalapp-mcp)

The same question twice within six hours costs one call, not two, because Kassalapp updates its prices once a day. The cache stays on your machine: Kassalapp's terms forbid publishing its prices.

The free plan allows 60 calls a minute. The plugin counts its calls and stops when Kassalapp says the minute's calls are used up. Then it answers from the cache, or asks you to try again in a minute. Its log of calls holds no search words and no barcodes. To see the count, here from a folder that has none:

$ kassalapp-mcp quota --state-dir /nonexistent/kassalapp-mcp
{
  "limit_per_min": null,
  "remaining": null,
  "seen_at": null,
  "calls_last_min": 0,
  "calls_today": 0,
  "cache_hits_today": 0,
  "429s_today": 0,
  "level": "ok",
  "backing_off_until": null,
  "headers": {}
}

The gates

Every one of these runs in continuous integration, and all of them run here:

$ uv run ruff check .
All checks passed!
uv run ruff format --check .   # layout
uv run mypy src                # types
uv run pytest -q               # behaviour
uv run python scripts/mutate.py  # that each rule's own test can fail

Only one mutation run goes at a time in a checkout. A run that was killed can leave a source file with a rule switched off. The next run puts it back, or uv run python scripts/mutate.py --repair-only does only that.

CONTRIBUTING.md says what each one is for, and decisions/ records the choices that shaped them, including how a change is made here.

Related MCP server: Marketfiyati MCP Server

Licence

GPL-3.0-or-later. See LICENSE.

Available Tools

2 tools
grocery_cheapestA
Read-only

Which chain is cheapest? Ranks the chains by their current price from Kassalapp; a price unchecked for 14 days never counts. 'product' is the words the person said, such as 'kaffe', or the name or barcode ('ean') of a choice the last answer offered.

Inputs: product (required). Returns: object

grocery_priceA
Read-only

What a grocery costs. The latest price per chain from Kassalapp, with the day it was checked. 'product' is the words the person said, such as 'lettmelk' or 'Tine lettmelk 1 liter', or the name or barcode ('ean') of a choice the last answer offered. 'chain' is a chain's name, such as 'Meny' or 'Joker'; omit it for every chain.

Inputs: product (required), chain. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    grocery_price returns per-chain prices for a product, while grocery_cheapest ranks chains by price — clearly different outputs, and the descriptions reinforce that. There is mild conceptual overlap since 'cheapest' is a derived view of the same price data, but the intended selection is unambiguous.

    Naming Consistency5/5

    Both tools use the exact same snake_case pattern with a shared 'grocery_' prefix and a short descriptive suffix (price, cheapest). Fully predictable naming.

    Tool Count3/5

    Two tools is thin for a price-comparison service: lookup and ranking are covered, but there is no search, chain listing, or history operation to round out the surface. It is defensible for a narrow purpose, but borderline sparse.

    Completeness3/5

    Core lookup by name/barcode and cheapest-chain ranking are present, but obvious gaps remain: no product search/discovery, no list-chains operation, and no price history or trend data. Agents can handle the main workflows but have no way to browse or resolve ambiguous queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and comparing product prices across Turkish supermarket chains (BIM, A101, Migros, SOK, etc.) with location-based filtering. Provides access to Turkish market data from marketfiyati.org.tr for price tracking and comparison.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to track global food prices, search products by barcode or name, and compare costs across 27 countries. It provides tools for real-time price scraping and data aggregation from major international supermarket chains.
      8
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Turns a spoken or typed grocery list into a ready Amazon Now cart by learning usual items from order history, prioritizing previously bought products, comparing prices, and filling the cart while leaving checkout to the user.
      6
      1
      MIT