Inspiration
An assistant should know not only today's answer, but what changed, what was wrong, and when nothing was known. A single current value cannot tell a moved meeting from a mistaken recollection. Memory gives remembered facts a history.
What it does
A browser-based simulated Alexa+ experience backed by a genuine self-hosted MCP server. Twenty deterministic tools remember, correct, withdraw and recall facts, answer "what was true on that date", share synthetic household messages, keep lists, profiles and projects, and give a daily brief. A sandboxed MCP Apps timeline shows replaced, withdrawn, expired and scheduled records. "Changed" and "wrong" are different: a corrected fact keeps its previous value; a withdrawn belief is kept as evidence together with how long it was believed. A scoped dashboard, snapshot export/import, archive-and-reset and optional voice input round out the demo.
How we built it
Python with the official MCP SDK 1.30.0 over Streamable HTTP (spec 2025-11-25), Starlette/Uvicorn, and a dependency-free local append-only memory core with two timelines: when a fact described the world, and when it was believed. The browser talks to the server with real MCP initialize, tools/call and resources/read; routing and tool execution are measured separately. Optional Amazon Bedrock routing exists but is off by default, with deterministic regex routing as the primary path. Optional Telegram bridge is disabled unless configured.
Challenges we ran into
- Natural-language routing must never turn a question into a write. We found and fixed a bug where "what is my name" stored the name "what"; routing now resolves read questions before declarations, and ambiguous text asks for clarification instead of writing.
- A fresh install pulled MCP SDK 2, which renamed FastMCP; we pinned and tested from a clean environment.
- The SDK's transport security defaults rejected every origin until we configured Host/Origin allowlists explicitly.
- MCP Apps timeline rendering needed a hand-built ui/initialize handshake.
Accomplishments we're proud of
- All 20 tools verified over real HTTP (24/24 wire scenarios) and 60/60 natural-language routing cases, including read-only cases that must not write.
- 140 automated tests pass in a fresh isolated environment, including real localhost server/browser journeys with reset, import and process restart.
- pip check and pip_audit report no known vulnerabilities.
- A written friction log of the Alexa+/MCP toolkit experience.
What we learned
Temporal truth is a product feature, not a storage detail. Strict separation between "intent routing" and "tool execution" makes safety testable. Pinned versions and fresh-install tests catch SDK drift early.
What's next
Real authentication and per-household identity, retention and deletion controls, multi-process storage and scaled-history benchmarks, and a certified Alexa+ add-on path. None of these are claimed today.
Synthetic simulation, not a certified Alexa add-on or tested Echo device. Speaker selection is not authentication. Voice input was tested with fixtures, not a real microphone.
Log in or sign up for Devpost to join the conversation.