What kind of data does the server use?
It uses a database seeded with realistic travel data specifically for the Phuket and Krabi regions in Thailand, covering day-wise hotel accommodations, transfers, and activities.
@Manjunatha-kv01
Basic information
Create a backend system for managing travel itineraries with the following components: 1. Database architecture for trip itineraries and models for the same using SQLAlchemy 2. RESTful API endpoints for creating and viewing itineraries 3. MCP server that provides recommended itin
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Full-Stack-Developer-Intern is an MCP server that returns recommended travel itineraries based on the number of nights. It is part of a backend system that includes a SQLAlchemy database schema for trip itineraries (covering hotel accommodations, transfers, and activities) and RESTful API endpoints (FastAPI) for creating and viewing itineraries, seeded with realistic data for the Phuket and Krabi regions in Thailand.
The server is used by providing a number of nights (2–8) to receive a list of recommended itineraries for that duration. It is implemented as an MCP server that exposes this functionality, though no specific client commands or configuration keys are detailed in the README.
It uses a database seeded with realistic travel data specifically for the Phuket and Krabi regions in Thailand, covering day-wise hotel accommodations, transfers, and activities.
Recommended itineraries are available for 2 to 8 nights.
The system uses SQLAlchemy for the database schema, FastAPI for RESTful API endpoints, and an MCP server for itinerary recommendations.
The MCP server itself only provides recommendations; creating and viewing itineraries is handled by separate FastAPI API endpoints described in the same project.
The README does not specify any authentication mechanisms or transport requirements beyond the MCP server implementation.
Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

AI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·
Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works.

Give your AI agent the ability to see any webpage. Capture screenshots from Claude, Cursor, or any MCP client. Supports full-page, dark mode, mobile emulation, OG image generation, base64 output, custom viewport, ad bloc

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
Comments