🌴 Travel Itinerary - FastAPI Project

Created By
ThasnimaShereefa year ago
This is a backend system for managing travel itineraries using FastAPI and SQLAlchemy, featuring RESTful APIs to create and view itineraries and an MCP server to recommend itineraries based on trip duration.
Overview

What is Travel Itinerary?

Travel Itinerary is a backend system designed for managing travel itineraries using FastAPI and SQLAlchemy, providing RESTful APIs to create and view itineraries, along with a Minimum Cost Path (MCP) server to recommend itineraries based on trip duration.

How to use Travel Itinerary?

To use Travel Itinerary, clone the repository, set up a virtual environment, install the dependencies, and run the development server. You can then access the API through the Swagger UI.

Key features of Travel Itinerary?

  • Create new itineraries with detailed day-wise breakdowns.
  • View all stored itineraries.
  • MCP server for recommending itineraries based on the number of nights.
  • Pre-seeded data for popular destinations like Phuket and Krabi, Thailand.
  • Interactive Swagger UI for testing API endpoints.

Use cases of Travel Itinerary?

  1. Planning travel itineraries for vacations.
  2. Recommending travel plans based on user preferences and trip duration.
  3. Managing and viewing multiple itineraries for different trips.

FAQ from Travel Itinerary?

  • Can I customize my itinerary?

Yes! You can create itineraries tailored to your preferences by adding hotels, transfers, and excursions.

  • Is there a live demo available?

Yes! You can access the live demo at Travel Itinerary Live Demo.

  • What technologies are used in this project?

The project is built using Python, FastAPI, SQLAlchemy, and SQLite.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ThasnimaShereef
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago