Skip to main content
Glama
Reese-max

Travel Planning MCP

by Reese-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Travel Planning MCP

No user-submitted related servers found.

    Related Servers

    • wanderlog-mcp

      joanhussein843
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to view and build complete trip itineraries through conversation, adding places, notes, hotels, transit legs, car rentals, checklists, expenses, and day headings. It also searches real-world places, hotels, and user-written travel guides, and can rename days, reorder blocks, and shift trip dates.
      173 npm
      MIT

    • wanderlog-mcp

      JaehyunRiccardi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible agents to view, create, and edit trip itineraries through conversation, adding places, notes, hotels, transit legs, car rentals, checklists, and budget expenses. Also supports searching places, guides, and hotel deals, plus updating trip dates, day names, and custom sections.
      173 npm
      MIT

    • wanderlog-mcp

      mTorres0999
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible agents to view and build trip itineraries through conversation, adding places, notes, hotels, transit, checklists, and expenses while managing dates and custom sections.
      173 npm
      MIT

    • wanderlog-mcp

      nshukla6150
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables conversational planning and editing of trip itineraries, including places, notes, lodging, transit, checklists, expenses, guides, and shareable links.
      173 npm
      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.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools cleanly map to distinct resources or actions, and the get_* read tools are generally easy to separate. get_trip_context intentionally overlaps with get_trip/get_place/get_reservation/get_constraints as an aggregate view, but its description clarifies that distinction.

    Naming Consistency5/5

    Tool names consistently follow a snake_case verb_noun pattern: get_, list_, search_, calculate_, validate_, create_, apply_, rollback_. The change-proposal family is especially predictable because every stage uses the same verb-first structure.

    Tool Count5/5

    At 15 tools, the set sits comfortably within the ideal range and each tool earns its place: reads, search, route calculation, proposal lifecycle, audit, and admin rollback are all represented. There is no obvious bloat or redundancy.

    Completeness4/5

    The surface covers trip/place/reservation/constraint reads plus a full validate-create-apply proposal workflow, audit trail, and rollback capability. Minor gaps exist around listing, updating, or deleting change proposals, but the core planning workflow is well supported and the mutation restrictions appear intentional.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources