Skip to main content
Glama
SpunkySarb

DoorDash MCP Server

by SpunkySarb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to DoorDash MCP Server

No user-submitted related servers found.

    Related Servers

    • doordash-mcp

      ashah360
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to search restaurants, browse menus, manage carts, and place orders on DoorDash programmatically. It utilizes a headless browser to interact with DoorDash's GraphQL API and bypass anti-bot protections for the full delivery lifecycle.
      22
      12 npm
      4
      MIT

    • doordash-mcp

      and2049
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to shop on DoorDash through 16 consumer tools covering account and order history, restaurant and menu browsing, cart edits, checkout previews, and order placement (including charging a saved card). It authenticates via a user-launched Chrome session on Windows and encrypts session and operation records with Windows DPAPI.
      16
      12 npm
      MIT

    • 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

    • DoorDash MCP Server

      chaituredd
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search restaurants, place delivery orders, and track real-time delivery status using the DoorDash Drive API. It includes a built-in mock data mode that allows for testing and demonstrating delivery lifecycles without requiring live API credentials.
      -
    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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: cart management (add/remove/list), menu/restaurant lookup (get_store_menu/search_restaurants), session checking (login_check), and order history. The descriptions make it easy for an agent to select the right tool for specific tasks like browsing versus ordering.

    Naming Consistency4/5

    The tools mostly follow a consistent verb_noun pattern (e.g., add_to_cart, get_store_menu, list_carts), with all using snake_case. The minor deviation is 'login_check' which uses a noun_verb structure instead of verb_noun, but this is a small inconsistency that doesn't significantly impact readability or predictability.

    Tool Count5/5

    With 7 tools, this server is well-scoped for DoorDash operations, covering key actions like browsing, cart management, and order tracking. Each tool earns its place without redundancy, making it manageable for agents while providing comprehensive functionality for the domain.

    Completeness4/5

    The tool set covers core DoorDash workflows: browsing (search_restaurants, get_store_menu), cart management (add/remove/list), session handling (login_check), and order review (order_history). A minor gap is the lack of a tool to place an order or checkout from the cart, which could limit end-to-end automation, but agents can still perform most tasks effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources