Gatherly AI: Alexa+ Home Hosting Assistant
Inspiration
Hosting friends and family should be about spending time together, not juggling multiple tasks, remembering shopping items, planning meals, and preparing the home.
I envisioned a simpler experience: what if someone could describe everything they needed in a single natural-language request and have an intelligent assistant coordinate the preparation?
That idea inspired Gatherly AI, a simulated Alexa+ experience designed to make hosting more effortless through contextual planning and coordinated actions.
For example, a host could ask for help preparing for guests arriving at 7 PM, mention that one guest is vegan, request a shopping list, schedule a reminder, and set a welcoming atmosphere. Instead of treating these as unrelated commands, Gatherly AI brings them together into one coordinated workflow.
My goal was to explore how conversational AI can move beyond answering questions and become a practical assistant that helps people accomplish everyday tasks.
What it does
Gatherly AI transforms a natural-language hosting request into a personalized plan and a series of coordinated application actions.
Key features include:
- Conversational interaction: Users describe their hosting plans in natural language.
- Context-aware planning: The assistant generates a preparation checklist and a menu that considers dietary requirements.
- Smart shopping lists: Ingredients can be organized into a shopping list, helping users prepare without overlooking important items.
- Reminder management: Users can create in-app reminders associated with their hosting schedule.
- Simulated smart-home controls: Users can select a welcoming lighting scene to represent the desired home atmosphere.
- Transparent action timeline: The interface shows the actions the assistant invokes and the corresponding results.
- Unified experience: Planning, shopping, reminders, and simulated home controls are brought together in one interface.
Rather than simply returning a conversational response, Gatherly AI is designed to make the results of supported actions visible to the user.
How I built it
I designed Gatherly AI as a web-based simulation of an action-oriented Alexa+ experience, following the hackathon's alternative approach for developers who are new to MCP.
The application is organized into two main layers:
Frontend: A React and Vite interface presents the conversation, hosting plan, shopping list, reminders, and simulated home-scene controls. The design focuses on clarity, responsive layouts, and making the assistant's actions easy to understand.
Backend: A Node.js and Express service handles requests, processes supported intents, validates tool inputs, and coordinates application actions.
The application is structured around five core tools:
create_hosting_plan— generates the preparation plan and menu.manage_shopping_list— manages the ingredients list.schedule_reminder— creates an in-app reminder.set_home_scene— updates the simulated lighting scene.get_home_status— retrieves the current application state.
The tool-oriented architecture separates request handling from individual actions, making the system easier to test, maintain, and extend.
I prioritized a deterministic demonstration flow so the core experience could be evaluated without depending on external AI credentials or restricted preview access. Where used, simulated home actions and reminders are clearly distinguished from real device integrations.
The architecture is intended to demonstrate interaction patterns relevant to the Alexa+ ecosystem without claiming that the application is an official Amazon product or a production Alexa+ integration.
Challenges I ran into
One of the main challenges was balancing an ambitious product idea with a limited hackathon development window.
Coordinating multiple actions: A hosting request can contain several requirements at once. I needed to structure these requirements into manageable actions instead of treating the request as a single text response.
Making actions meaningful: A conversational interface is not enough to demonstrate an action-oriented assistant. The application needs to reflect successful operations in its shopping list, reminder panel, and home-scene controls.
Working within integration constraints: Native Alexa+ preview capabilities and device integrations may not be available to every developer. I therefore focused on a simulated web experience that could demonstrate the intended interaction without depending on restricted access.
Maintaining reliability: The application needs to remain useful even when optional external services are unavailable. A deterministic core workflow reduces dependencies and makes the demonstration more predictable.
These challenges reinforced the importance of choosing a clear scope, validating actions, and prioritizing a complete user journey over unnecessary complexity.
Accomplishments that I'm proud of
I am proud of the product direction and the effort to bring several everyday hosting tasks into one coherent experience.
- Designed a focused use case that demonstrates the potential of contextual, conversational assistance.
- Organized the application around separate, reusable tools rather than one monolithic response handler.
- Connected the hosting workflow with shopping, reminders, and simulated home-scene controls.
- Emphasized visible action results so users can understand what the assistant has done.
- Prioritized an accessible demonstration that does not require restricted Alexa+ preview access.
- Established an architecture that can evolve toward more advanced AI and MCP-based integrations.
Most importantly, Gatherly AI explores a practical vision of an assistant that helps users coordinate tasks instead of simply providing information.
What I learned
This project strengthened my understanding of agent-oriented application design and the distinction between conversational intelligence and action execution.
I learned that a useful assistant needs more than natural-language input. It also needs structured intent handling, clearly defined tools, input validation, observable results, and reliable error handling.
I also learned the importance of designing around the user's complete journey. A successful interaction should connect the initial request to a useful plan and meaningful application-state changes.
Finally, working within a short development window highlighted the value of prioritization. A focused, reproducible demonstration can communicate a product's value more effectively than a large collection of incomplete features.
What's next for Gatherly AI: Alexa+ Home Hosting Assistant
Gatherly AI is a starting point for a more capable, context-aware home assistant.
My next steps include:
- MCP integration: Implement a compliant MCP server using the official SDK and Streamable HTTP transport where appropriate, enabling standardized discovery and execution of supported tools.
- More advanced planning: Improve how the assistant handles follow-up requests, changing schedules, preferences, and multiple constraints.
- Real smart-home connectivity: Explore supported integrations that can control compatible devices with appropriate permissions and user confirmation.
- Persistent reminders: Introduce reliable scheduling and notification delivery beyond the current in-app simulation.
- Personalization: Support reusable preferences for dietary requirements, household routines, and hosting styles.
- Improved testing: Expand automated tests for tool execution, invalid inputs, failures, and complex hosting scenarios.
- Alexa+ ecosystem exploration: Investigate the supported integration pathways and developer resources needed to evolve the simulated experience into a standards-based implementation.
My long-term vision is to make Gatherly AI an assistant that helps people spend less time coordinating tasks and more time enjoying the moments that matter.
Built With
- express.js
- javascript
- mcp
- node.js
- react
- restapi
- typescript
- vite
Log in or sign up for Devpost to join the conversation.