plantmenu
README.md
# plantmenu
Looking for somewhere to eat where the vegan options are real dishes rather than an afterthought? plantmenu is a small local bridge to the hosted KaleMap MCP service: it searches the vendor's saved restaurant and menu data, surfaces places by their vegan status and score, previews dishes at a single restaurant, pulls detailed menu evidence with dietary labels, and lists places near a coordinate or in a covered city.
Nothing is scraped or stored on your own machine. This package answers `tools/list` locally from the captured tool definitions and forwards every `tools/call` to the hosted service over a streamable-HTTP JSON-RPC session, returning whatever the service sends back unchanged.
## The tools
All six tools read saved data; none of them triggers scraping.
- **`get_menu`** — Detailed saved menu evidence for one place, by `slug`: twelve dietary labels, provenance, freshness and explicit unknowns. Per its captured description it requires a developer API key or a consented OAuth connection, and each call uses one trial or paid request from the caller's own plan. Follow its pagination even when filtered pages are empty, and cite the restaurant and source URLs it returns.
- **`search_places`** — Search restaurants by name, via `query`. Each match comes back with its vegan status, a score from 0 to 100 (100 means fully vegan), its city and its page URL.
- **`place_vegan_options`** — A free preview of up to four saved dishes at one restaurant, by `slug` — for example the last path segment of a place URL from a search result.
- **`places_near`** — Restaurants near a `lat`/`lng` coordinate, nearest first, with status, score and the best dishes of each. Optional filters include a radius in kilometres, an `only` mode, a result limit, and `needs`: dietary needs that a single dish must satisfy all at once.
- **`city_vegan_places`** — The most diet-friendly places in a city, by city slug, fully vegan first. Accepts the same `only`, `needs` and limit ideas as `places_near`; city slugs come from `list_cities`.
- **`list_cities`** — Every city the service covers, with its slug and how many vegan-friendly places it has. It takes no arguments.
The dietary labels used across the surface are: vegan, vegetarian, pescetarian, gluten-free, dairy-free, egg-free, peanut-free, tree-nut-free, shellfish-free, fish-free, soy-free and sesame-free. Labels are read from menus, so allergy decisions should still be confirmed with the kitchen.
## Install and run
As an MCP server via npm:
```bash
npx -y @reneturcios/plantmenu mcp
```
MCP client configuration:
```json
{
"mcpServers": {
"plantmenu": {
"command": "npx",
"args": ["-y", "@reneturcios/plantmenu", "mcp"]
}
}
}
```
As a container:
```bash
docker run -i ghcr.io/cloudcorprecords/plantmenu
docker run --rm ghcr.io/cloudcorprecords/plantmenu list_cities '{}'
```
## CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
```bash
plantmenu search_places '{"query":"bulla"}'
plantmenu get_menu '{"slug":"some-place-abc1234"}'
plantmenu place_vegan_options '{"slug":"some-place-abc1234"}'
plantmenu places_near '{"lat":25.7617,"lng":-80.1918}'
plantmenu city_vegan_places '{"city":"miami-us"}'
plantmenu list_cities '{}'
plantmenu --version
```
Exit codes: `0` when the forwarded call succeeds, `1` when the upstream result is an error, and `2` for usage problems such as an unknown subcommand or a malformed JSON argument.
## Configuration
- `KALEMAP_MCP_URL` — Overrides the upstream endpoint. The default is the pinned hosted endpoint, `https://kalemap.com/mcp`. (The override variable is a reconstruction added by this rebuild.)
- `KALEMAP_API_KEY` — When set, its value is sent to the upstream on every request as an `Authorization: Bearer <value>` header. When it is not set, no key header is sent at all, matching the keyless behaviour the tool surface was captured with. (The variable name and the Bearer form are reconstructions; the hosted service's registry record declares an `Authorization` header, not marked required.)
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with `plantmenu error:`.
## How forwarding works
The first forwarded call opens a session: an `initialize` request (protocol version `2025-03-26`), followed by a `notifications/initialized` notification, then the `tools/call` itself. If the service answers the initialize request with an `Mcp-Session-Id` header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any `isError` flag and any extra fields the service includes.
## Development
```bash
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
```
The test suite checks the served tool list against the captured surface tool by tool, exercises the session handshake and its reuse, covers both key-header branches, and verifies that arguments go upstream untouched and results come back untouched.
## License
MIT — see `LICENSE`. Copyright (c) 2026 Rene Turcios.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues