listonic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LISTONIC_EMAIL | Yes | Listonic account email (required). | |
| LISTONIC_LIST_ID | No | Pin a default list; see get_lists for the ids. | first list |
| LISTONIC_PASSWORD | Yes | Listonic account password (required). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_listsA | All shopping lists on the account, with their ListIDs. Use when the user has several lists ("weekend BBQ", "pharmacy") — every other tool takes an optional list_id to target one; without it they use the default list (the pinned --list-id, or the account's first list). |
| get_itemsA | Fetch the grocery list. Call this FIRST before editing/deleting, to get ItemIDs. Checked items ([x]) = the user most likely already HAS them at home. Unchecked items ([ ]) = still to buy. Args: list_id: which list (from get_lists). Empty = the default list. |
| add_itemsA | Add one or MANY items in a single call — batch whole recipes, don't loop. Args: items: the items to add. list_id: which list (from get_lists). Empty = the default list. |
| edit_itemsA | Edit one or MANY items in a single call — most often to check/uncheck while shopping ("got the milk"). Args: items: edits to apply; only the fields you set are changed. list_id: which list (from get_lists). Empty = the default list. |
| delete_itemsA | Delete items entirely (not check off — that's edit_items with is_checked). Args: item_ids: ItemIDs to delete (from get_items). list_id: which list (from get_lists). Empty = the default list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: get_lists retrieves all lists, get_items fetches items from a list, add_items adds items, edit_items modifies items, delete_items removes items. No overlapping functionality.
All tools follow a consistent verb_noun pattern (get_lists, get_items, add_items, edit_items, delete_items) with no deviations.
5 tools is appropriate for a grocery list management MCP server, covering the core operations without being too few or excessive.
The tool set covers item CRUD operations fully but lacks list management tools (create, update, delete lists). This is a notable gap that may hinder user workflows requiring new list creation or deletion.