-
-
client-main-page
-
client-dashboard-page-1
-
client-dashboard-page-2
-
client-dashboard-page-3
-
client-dashboard-page-4
-
client-mcp-ui-1
-
client-mcp-ui-2
-
client-mcp-ui-3
-
client-mcp-ui-4
Inspiration
A U.S. Census Bureau suggests that a person in the U.S. could move 11–12 times in their lifetime. Moving can be exciting, but figuring out housing, costs, routes, and local services takes a lot of work. I wanted to make it easier.
What it does
MoveFlow helps you plan a move through a conversation. It brings together rental options, cost estimates, routes, and local services in one place. You can also update your plan as your needs change.
How I built it
I built MoveFlow with Next.js, TypeScript, and a self-hosted MCP server for the Alexa+ hackathon. I used OpenAI, Neon, RentCast, Mapbox, and TomTom for planning, saved plans, housing, routes, and local searches.
Challenges I ran into
Getting the MCP UI to work smoothly in Codex chat took some trial and error. Getting access to a flight API was also harder than I expected, so the current flight examples are illustrative and can't be booked.
Accomplishments that I'm proud of
I'm proud that I built a working MCP server and dashboard that can take a simple moving request and turn it into a useful plan.
What I learned
I learned how to build MCP tools for a multi-step workflow, ask for missing details, and bring data from different providers together.
What's next for MoveFlow
I want to improve the experience across more assistants, add real flight data, and make MoveFlow even more helpful throughout the moving process.
Built With
- mapbox-api
- mcp
- mcp-apps
- neon
- next.js
- openai-api
- postgresql
- react
- rentcast-api
- tailwind
- tomtom-api
- typescript
- vercel
