Built a Travel App with AGNT MCP in 3 Days

A solo developer building a Bali travel planner needed real-time venue data — hours, menus, availability, reviews — but didn't want to scrape dozens of sources or negotiate individual API partnerships.

Existing travel APIs (Google Places, TripAdvisor) provided generic data without booking capability. The developer wanted a single integration that could both search venues and handle reservations.

The app was built on a Claude Code + MCP stack, so any integration needed to work as an MCP server — not a REST API bolted on as an afterthought.

The developer connected AGNT's MCP server to their existing Claude Code environment. The MCP server exposes venue search, availability check, and booking creation as native MCP tools — no REST wrapper needed.

Using AGNT's API quickstart prompt and MCP server scaffold prompt (both from the Developer Quickstart Pack), the developer had a working prototype in under 4 hours.

The A2A integration test prompt validated the full booking flow end-to-end before the app went live. Total glue code: fewer than 200 lines.

The app shipped in 3 days — from first API call to production deployment. Without AGNT's MCP server, the developer estimated 3-4 weeks to build equivalent venue data coverage.

The app now handles 12,000 API calls per day, searching across 800+ Bali venues with real-time availability.

Booking conversion rate is 3x higher than the developer's previous implementation because AGNT's agent handles the full reservation flow including confirmation and reminders.

The developer has since open-sourced the MCP integration layer, which has been forked by 40+ other travel app builders.