🌏 Travel Itinerary Backend System — Full Stack SDE Assignment
LocalAbout 🌏 Travel Itinerary Backend System — Full Stack SDE Assignment
This FastAPI and SQLAlchemy backend manages day-by-day travel itineraries for destinations including Phuket and Krabi. It supports itinerary creation and browsing, plus non-AI recommendations based on the number of nights.
Key features
- 01Create day-by-day itineraries
- 02View existing itineraries
- 03Recommend itineraries by night count
- 04Include hotels, transfers, and activities
Use cases
- 01Create a multi-day Phuket trip plan
- 02Browse stored travel itineraries
- 03Find a plan based on trip length
MCP support
The project includes an MCP server that provides recommended itineraries.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README🌏 Travel Itinerary Backend System — Full Stack SDE Assignment
This project is a backend system built with FastAPI and SQLAlchemy, designed to manage and recommend travel itineraries for regions like Phuket and Krabi in Thailand. It supports the creation, viewing, and recommendation of day-wise itineraries.
✅ Features
- 🧳 Create detailed travel itineraries (day-wise breakdown)
- 🗂 View all existing itineraries
- 🧠 Get AI-free recommended itineraries by number of nights
- 🏨 Support for hotel stays, transfers, and activities per day
🛠 Tech Stack
- Python 3.10+
- FastAPI
- SQLAlchemy
- SQLite (for local dev)
- Pydantic
📦 Setup Instructions
1. Clone the repository
git clone https://github.com/21471A0505/travel-itinerary-backend.git
cd travel-itinerary-backend
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.