Skip to main content
Glama
mtpajula

Tekuila MCP Server

by mtpajula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Tekuila MCP Server

No user-submitted related servers found.

    Related Servers

    • foodvisor-mcp

      cldt-fr
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server integrating Foodvisor nutrition API for food search, meal logging, daily summaries, and progress tracking via LLM agents like Claude.
      MIT

    • DietBox MCP

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for nutritionists to manage patients, prescriptions, anthropometry, and meal plans, integrating with Claude, Cursor, and other AI agents.
      MIT

    • @mealmastery/mcp-server

      MealMasteryAI
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for MealMastery AI meal planning that enables users to manage meal plans, recipes, and grocery lists through natural language conversation with AI agents like Claude.
      33 npm
      MIT

    • recipe-mcp

      valetdotdev
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for AI-powered recipe generation and transformation, enabling users to create custom recipes from natural language descriptions and modify existing ones to meet dietary and nutritional goals.
      2
      29 npm
      1
      MIT

    • cronometer-mcp

      cphoskins
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that provides access to Cronometer nutrition data, enabling users to pull food logs, macro and micronutrient summaries, and biometric data into Claude or Cursor. It supports daily nutrition tracking and raw CSV exports by interfacing with the Cronometer web protocol.
      27
      22
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 5 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. 'analyze_daily_menu' and 'get_current_day_menu' both target today's menu, with the former adding AI analysis instructions. Similarly, 'get_current_week_menu' and 'plan_weekly_menu' both handle the weekly menu, with the latter including planning instructions. This overlap makes it unclear which tool to use for basic retrieval versus enhanced functionality.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'analyze_daily_menu' and 'get_current_date'. However, there is a minor inconsistency: 'get_current_day_menu' and 'get_current_week_menu' use 'day' and 'week' inconsistently with 'daily' and 'weekly' in other tools, but overall the naming is predictable and readable.

    Tool Count5/5

    With 5 tools, the count is well-scoped for a restaurant menu server focused on daily and weekly planning. Each tool appears to serve a distinct role in the domain, and the number is neither too sparse nor overwhelming, fitting typical expectations for such a purpose.

    Completeness3/5

    The tool set covers retrieval and planning for daily and weekly menus, but there are notable gaps. For example, there are no tools for updating or modifying menus, handling past or future menus beyond the current period, or managing restaurant details like hours or locations. This limits the server's ability to support full lifecycle operations in the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources