Revamp

What revamp MCP server does

The revamp MCP server listing is described as a way to search Revamp Travel’s Armenia catalog, check availability, and plan trips. The catalog covers places to stay, restaurants, tours, and regional experiences. An interactive Armenia atlas, editorial content, category filters, text search, and regional filtering are part of the broader application described by the repository.

The supplied source is a full-stack travel marketplace rather than a documented MCP package. Its client is a React and TypeScript single-page application. Supabase provides authentication, Postgres storage, and Row-Level Security for accounts and listings. An Express API handles the AI trip planner and link-based listing prefill. No MCP SDK, transport, manifest, or named MCP tool definitions appear in the provided material.

How it works

Published listings are read from Supabase when the application has its configuration. Without Supabase variables, the interface falls back to static seed data in read-only mode. The trip planner sends requests to the server, which calls Anthropic and grounds day-by-day itineraries in the live published catalog.

Operators can create, edit, and delete their own stay and tour listings through the dashboard. New submissions and resubmissions pass through an administrator review gate before publication. Restaurants remain editorial or seed content. The application uses Supabase policies to enforce ownership rather than relying only on client-side checks.

For the revamp MCP server use case, these details describe the underlying travel capabilities, but they do not establish how an MCP client would discover or invoke them.

Setup and configuration

The repository requires Node.js 22 or newer, pnpm 10 or newer, and a Supabase project for real accounts and listings. Local setup uses pnpm install, a copied .env file, and pnpm dev. The development command starts Vite and the Express API together; Vite proxies API requests to the default API port of 3001.

Set VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY to connect the application to Supabase. ANTHROPIC_API_KEY enables the /plan itinerary feature. Database migrations must be applied in order before using real accounts, listings, review controls, and Row-Level Security. The repository also documents service-role and seed-account variables for local catalog seeding.

Limitations and notes

Payments are not implemented. Booking controls show a sign-in prompt for signed-out users and a disabled “Payments coming soon” state for signed-in users. Displayed listing rates are stored values, but the application does not charge them.

The supplied material does not document an MCP server, supported MCP clients, transport details, or callable tool names. Treat the revamp MCP server label as unverified until an MCP-specific implementation or interface description is provided.