- Built for
- Alexa+ customers who plan a trip by voice
- When
- November 2026
10tools Alexa+ can call
0wrong plans on impossible requests
89 msmedian planning time
Many AI travel agents let a language model write the itinerary and then ask the user to check it. A plan that sounds right can still break a rule, like a connection that is too tight or a day over budget, and over a voice assistant nobody can see the plan to catch it.
Alexa+ connects to outside services through MCP. Plexis is an MCP server that plugs into Alexa+ as an add-on. It gives Alexa+ ten tools: plan a trip, change it, explain a choice, check better dates, book it, get a travel brief, call a hotel front desk, remember household preferences, show trip status, and verify a receipt. Alexa+ talks to the customer; Plexis does the deciding.
The plan comes from a solver, not from a language model. When a request cannot be met, Plexis finds the smallest set of clashing rules, works out the smallest change that fixes them, and solves again to show the change works. A second tool, Z3, confirms independently that the conflict is real.
The server speaks MCP over Streamable HTTP. A deterministic parser turns speech into 21 kinds of rule, a CP-SAT model chooses flights, stays, meals and activities and schedules each day, and Z3 confirms impossible requests. Every plan goes into a ledger: hashed, chained to the previous entry and signed with Ed25519, so any edit can be detected.
Eight simulated partner services (transport, stays, dining, attractions, weather, a wallet, front-desk calls and destination research) sit behind it, and delays, errors and cancellations can be injected to test recovery. A voice client uses Pipecat, and a React simulator acts as an MCP client with a visible trace and proof view. It ships in Docker with 105 tests, and CI runs lint, security checks, tests and a benchmark.
On my own benchmark of 80 seeded requests (70 solvable, 10 impossible), every plan passed every check and no impossible request got a wrong plan, against 13.8% and 25.0% plan pass rates for two greedy baselines. Median planning time was 89 ms.
It is a functional prototype. Native Alexa+ deployment needs partner access, so it is demonstrated through an MCP-compatible Alexa+ simulator, and the travel and payment services are simulated, not live.
- Python
- MCP
- OR-Tools CP-SAT
- Z3
- LangGraph
- Amazon Bedrock
- Strands Agents
- Pipecat
- React
- TypeScript
- SQLite
- Docker
- GitHub Actions
How it works
- 1Say itYou tell Alexa+ something like “Plan a weekend in Portland with Grandma under fifteen hundred dollars”. Alexa+ passes your words to Plexis, which asks for one missing detail at a time.
- 2CompilePlexis turns the words into exact, typed rules in about a millisecond. No language model decides anything at this step.
- 3SolveIt collects flights, stays, restaurants, activities and weather from partner services, and a CP-SAT solver picks a plan that meets every rule.
- 4VerifyA separate checker that shares no code with the solver recomputes every rule and price. Only a plan that passes everything is spoken.
- 5ExplainAsk “Why not the Harbor Inn?” or “Make it cheaper”. If a request is impossible, Plexis names the rules that clash and the smallest fix, and proves the fix works.
- 6BookSay “Book it”. Plexis confirms the total, books through a hold-and-confirm flow that can undo itself, and signs a receipt you can check later.