Skip to main content
Glama
matiasconcha11

Uber Eats MCP Server

by matiasconcha11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Uber Eats MCP Server

No user-submitted related servers found.

    Related Servers

    • ijburgeats-mcp

      jspuij
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to browse restaurants and menus, manage a cart, reorder past orders, review checkout details, and place food delivery orders, returning a payment link to complete payment.
      13
      MIT
    • Canuckeats MCP by canuckeats

      Canuckeats MCPofficial

      canuckeats
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to browse menus and place real food delivery orders from UberEats and DoorDash across 89 Canadian cities.
      1
      -

    • ubereats-mcp

      Saekisui
      A
      license
      A
      quality
      D
      maintenance
      Enables an AI agent to search stores and dishes, browse menus, add items with options and quantities, and read a checkout snapshot inside the user's own logged-in Chrome session, placing an order only after explicit approval. Ordering is gated behind a review step with a one-time confirm token, spend caps, and post-order delivery tracking, while card numbers and addresses never appear in the conversation.
      8
      12
      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

    A3.6/5.0

    Scored across 34 tools

    Disambiguation3/5

    Most tools are clearly separated by domain (address, cart, checkout, orders, search, preferences), but there are some ambiguous boundaries. uber_eats_get_address vs uber_eats_saved_addresses vs uber_eats_set_address overlap conceptually, and uber_eats_track_orders vs uber_eats_track_active_orders overlap heavily. Checkout tools (checkout_preview, checkout_savings, set_checkout_tip, set_checkout_payment) are distinct but close enough that an agent could misselect.

    Naming Consistency4/5

    All tools follow the uber_eats_ prefix with consistent snake_case. Most use verb_noun structure (search, track, view, remove, set). Minor inconsistencies: 'whoami' and 'recommend' and 'reorder' lack a noun object, and 'build_taste_profile' uses adjective rather than a direct action on a noun. Overall naming is quite predictable.

    Tool Count3/5

    34 tools is on the heavier side. The domain genuinely has many facets (search, browsing, cart, checkout, payment, orders, preferences, recommendations, profiles, favorites), so the count is defensible, but it borders on excessive and could clutter an agent's tool selection. Some tools like track_orders vs track_active_orders could be merged.

    Completeness4/5

    The coverage is thorough: search, browse, menu, items, cart CRUD, checkout flow, payment, promo, tips, orders tracking, reordering, profiles, preferences, favorites, and recommendations. Minor gaps include lack of explicit remove-payment-method or a dedicated order-cancel tool, and reorder doesn't fully perform the action (only surface items for re-add). Overall the lifecycle from search through ordering to tracking is well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources