Inspiration
Customer conversations often lead to several administrative tasks. AutoIA connects customer lookup, calendar checks, appointment booking and follow-ups in one consistent workflow.
What it does
AutoIA exposes five working MCP tools: find_customer, get_calendar_availability, create_appointment, add_followup and list_pending_followups.
The browser demo searches fictional customers, checks availability, books an appointment, verifies that the slot becomes occupied, and records and retrieves a pending follow-up. All confirmations come from actual server responses.
How we built it
We used Node.js 24+, TypeScript and the official MCP packages, with MCP 2025-11-25 and Streamable HTTP. Tools delegate to business services and in-memory repositories. The HTML, CSS and JavaScript interface communicates directly through MCP initialization, discovery and tool calls.
Challenges
We maintained shared state across requests, reused calendar conflict rules, handled identical write retries, and prevented internal diagnostics from leaking through public errors.
Accomplishments
The five-tool workflow runs end to end. All 219 automated tests pass, and real-browser checks verify appointment persistence, follow-up retrieval and responsive presentation.
What we learned
A useful MCP workflow needs consistent domain rules and verifiable outcomes. Protocol tests and browser checks provide complementary evidence.
What's next
This MVP uses fictional data and process-local memory. Durable storage, production authentication and authorized assistant integration are future work. Direct Alexa+ integration, AWS services, external calendars and notifications are not implemented.
Built With
- css
- html
- javascript
- mcp
- node.js
- playwright
- typescript
- vitest
- zod
Log in or sign up for Devpost to join the conversation.