Errand Runs MCP Server
Related Servers
Alternatives to Errand Runs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables local shopping research by reading the products, SKUs, stores, reviews and images actually loaded in a logged-in Chrome session, supporting product search and filtering, exact SKU selection and comparison, in-store and store research, favorites management, and authorized single-send merchant inquiries with reply retrieval. Runs entirely on the local machine with traceable research records, and is also exposed via CLI and a local web entry.MIT
- AlicenseNot gradedqualityCmaintenanceEnables household tracking of tools and consumables, tool lending and returns, maintenance reminders, project gap shopping lists, and seasonal tune-up prompts through natural language, with local JSON storage and backups.MIT
- FlicenseAqualityDmaintenanceEnables tracking personal expenses by adding, listing, deleting, and summarizing expenses by day or month, stored locally in a JSON file.4-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables tracking of household food consumption, expiration decay, and dietary filters to synthesize optimized grocery carts within budget constraints.-
- AlicenseAqualityBmaintenanceEnables users to track job and internship applications, statuses, deadlines, and interviews, with upcoming reminders and CSV or Markdown export. It runs locally and stores data in a single JSON file without network calls, accounts, or API keys.8115 npmMIT
- AlicenseBqualityBmaintenanceEnables local management of household pet care notes—vet-visit histories, medication organizers, weight trends, feeding notes, and groomer/sitter handoff summaries—stored in plain JSON files over MCP stdio with no network calls.13MIT
TDQS
Scored across 6 tools
Each tool has a fairly distinct role: logging (log_item), aggregate views (tally), planning (plan_run), closure (mark_bought), historical query (receipt), and filtered listing (list_items). The only mild overlap is between tally and list_items, both read views, but their descriptions clearly differentiate grouped-by-store counts from item-level status filtering.
Four tools follow a clean verb_noun or verb_object pattern (log_item, list_items, mark_bought, plan_run). The remaining two (tally, receipt) are bare/single-word names, which is a minor deviation but still readable and semantically apt.
Six tools is a tight, well-scoped surface for a personal errand-planning server. Every tool maps to a distinct stage of the workflow (log, review, plan, close, report, audit) with no filler.
The lifecycle of logging, planning, closing, and reporting is covered, but there is no way to update an item (fix quantity, retag a store) or delete/undo a mistakenly logged entry or purchase. These are notable gaps that would force workarounds for common corrections.