Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Lodge Is room 204 free for study this afternoon?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The porter's lodge that never closes.
A self-hosted MCP server that answers campus questions by voice —which room is free, where the class moved to, when the deadline falls— running on the systems any institution already has.
Build, Ship, Shape: Amazon Developer Hackathon 2026 · Track Alexa+ · MCP · Mini-challenges: AWS Builder and Open Source.
What the porter knows lives in no system. It is scattered across a timetable pinned to a wall, an email from the registry, the academic calendar and twenty years of memory. And it is only reachable while the lodge is open.
Lodge exposes that knowledge as an MCP server so any agent can answer it at any hour. The decision that defines the project: it is not built for one university. It is built against the standards they all already use —iCalendar feeds, an LDAP directory, a room inventory in a table— so that an institution deploys it in an afternoon instead of commissioning an integration.
Why MCP and not one more chatbot. Campus assistants live inside a widget, cannot be composed and die with the contract. An MCP server is the opposite: any agent can consume it. Alexa+ on a speaker today; the student's laptop assistant or the teaching platform tomorrow. The institution publishes its capabilities once and stops picking a client.
Related MCP server: upv-mcp
Published according to capabilities — nothing appears if the adapter does not support it. Write tools
confirm before acting through a multi-turn request: they return input_required and the client
retries with the answer.
Tool | Question it answers | Level |
| "Where can I study right now?" | read |
| "What do I have first thing tomorrow?" | read |
| "When does enrolment close?" | read |
| "How do I get to the exam room?" | read |
| "The projector in room 203 won't start" | write |
| "Any news on the fault I reported?" | read |
Acceptance criteria for each: docs/use-cases.md.
Generalising is the classic scope trap. The discipline is numerical: one adapter fakes the seam, three are goldsmithing, two force it to be real.
Adapter | Source | Purpose |
| Deterministic generator | Reference, demo, reproducibility. It is the University of San Telmo |
| iCalendar · LDAP · CSV | What any institution already has, with nothing to build |
Explicitly out of scope: connectors for specific teaching platforms. They are the natural first addition after the hackathon.
🚧 Under construction. Milestone M0 (foundations) — the code lands from M1 on.
Milestone | Dates | Output |
M0 | 15–17 Sep | Reference dataset closed |
M1 | 18–27 Sep | Answers a generic MCP client |
M2 | 28 Sep–4 Oct | The seam is real, not a promise |
M3 | 5–11 Oct | Full end-to-end conversation |
M4 | 12–16 Oct | Two deployment targets working |
M5 | 17–20 Oct | Installable by a stranger |
M6 | 21 Oct | Submitted |
Full plan, architecture, pinned versions and cut rules: RUNBOOK.md
(versión en español).
MCP client (Alexa+ / our own orchestrator / any agent)
│
▼
MCP server ── Streamable HTTP, stateless, server/discover
│
▼
Provider interface ── capabilities + locale
│
┌────┴────┐
▼ ▼
synthetic standards
(San Telmo) (iCalendar · LDAP · CSV)The core runs anywhere; AWS is a destination, not a requirement. A project that hopes to be adopted by any institution cannot demand a cloud account. Two first-class deployment targets:
Self-hosted — distroless container plus a compose file. One config file and your own credentials.
Managed — AWS Lambda · DynamoDB · CDK v2. The documented path for the AWS mini-challenge.
Node 24 LTS
An MCP client speaking MCP revision 2025-11-25 over Streamable HTTP
For the managed target only: an AWS account with Bedrock access in us-east-1
Installation instructions land in M5, and they are validated against the clock on a clean machine by someone outside the project. Until then this section is deliberately empty rather than aspirational.
The University of San Telmo is fictional: three buildings, six degree programmes and an academic calendar, all generated, not anonymised. This project contains no data, branding, systems or naming from any real institution, and requires authorisation from none.
The server returns data belonging to whoever is asking, stores no student records and runs on the institution's own infrastructure.
Apache-2.0 — see NOTICE.
This server cannot be deployed
Send tasks and notifications to people's phones. Answers build a queryable knowledge base.
GDPR-compliant calendar access for AI assistants: read, create, edit, RSVP. Google, MS 365, Apple.
Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
