Skip to main content
Glama

Related Servers

Alternatives to DoorDash MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • F
      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
      3
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants in Cursor and other MCP hosts to connect to a company REST API, handling token-based authentication, read-only lookups, and guarded job/package creation with optional shipping labels.
      0
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables delivery tracking through the Parcel API, including listing and fetching deliveries, searching carriers, and adding new deliveries with optional write protection and multiple credential methods.
      5
      6 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to search restaurants, browse menus, and manage DoorDash carts through structured JSON data. It leverages a background browser to handle authentication and direct GraphQL API calls for efficient interaction.
      7
      2
      -

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific actions in the delivery lifecycle: create_quote, accept_quote, create_delivery, get_delivery, update_delivery, and cancel_delivery. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_delivery_quote, accept_delivery_quote, cancel_delivery). The naming is predictable and uniform throughout the set.

    Tool Count5/5

    With 6 tools, this server is well-scoped for managing deliveries, covering the essential lifecycle from quoting to completion. Each tool earns its place without being excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the delivery domain: create (quote and delivery), read (get), update, and delete (cancel). There are no obvious gaps, and agents can handle typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues