Skip to main content
Glama
chrischall

myhotlunchbox-mcp

by chrischall

Related Servers

Alternatives to myhotlunchbox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables reading and writing MyFitnessPal data—including food diary entries, custom foods, saved meals, recipes, exercise, measurements, water, and nutrition goals—through 33 MCP tools using your existing browser session for authentication.
      33
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables interacting with the Lunch Money personal finance API through MCP tools for retrieving user info, transactions, and performing calculations, with minimal response sizes.
      6
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the Löwen Menü IBS5 school-lunch ordering system, enabling an LLM to browse weekly menus, manage a shopping cart, and place meal orders.
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and interact with ManageBac accounts, including deadlines, grades, GPA, announcements, resources, and assignment submission, through a locally run MCP server with a saved browser session.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with the Paxaver school lunch platform, allowing users to check menus, order lunch, manage wallet funds, register for events, donate, and perform administrative tasks like managing restaurants and menu items.
      208 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Microsoft Outlook via Graph API. 20 consolidated tools for email, calendar, contacts, folders, rules, categories, and settings with safety controls (dry-run preview, rate limiting, recipient allowlists) and MCP annotations on every tool.
      22
      922 npm
      36
      MIT

    TDQS

    A3.7/5.0

    Scored across 35 tools

    Disambiguation4/5

    Each tool maps to a distinct resource and action (students, orders, cart, transactions, coupons, gift cards, subscriptions), and the read/form/write variants are clearly separated. A few adjacent pairs like get_day vs get_menu and get_order_form vs create_order could be confused, but the descriptions are explicit enough to prevent misselection.

    Naming Consistency4/5

    Every tool uses the mhlb_ prefix and nearly all follow a verb_noun pattern such as list_students, create_order, and apply_coupon. A few exceptions like healthcheck, whoami, and session_reset break the pattern, making the naming strongly consistent but not perfect.

    Tool Count2/5

    35 tools crosses the 25+ threshold for a heavy tool surface, and many are narrow single-purpose helpers like get_cart_tabs, init_checkout, and the various *_form endpoints. The count makes the set harder to scan even though most tools individually serve a purpose.

    Completeness4/5

    The surface covers the full parent-facing lifecycle: session, student CRUD, menu/order/cart/checkout, transactions, coupons, gift cards, subscriptions, and printable PDFs. Minor gaps exist, such as no generic order-history listing and no payment-method management beyond what init_checkout reports, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive