Account boundaries first
Account-scoped access and browser OAuth connect the assistant to the correct calendar without treating a conversation as permission to access someone else’s data.
CASE 01 / AI-connected products
nambli.
A calendar that speaks agent.
Connecting a private calendar to conversational workflows, with account boundaries and explicit control over changes.
- MY ROLE
- Product engineering & MCP integration
- CONTEXT
- Tor Production · Independent product
- TOOLKIT
- MCP · OAuth · Cloudflare · Calendar API
CONVERSATION → ACTION
Make room for the next idea.
MCP
nambliYOUR TIME, CONNECTED
1234567891011121314
Space to build 14:00
01 / THE CHALLENGE
What needed to work.
Make calendar work available inside a conversation while keeping account ownership, local time and existing records unambiguous.
02 / THE ENGINEERING
Where I made a difference.
Changes with context
Timezone-aware workflows and revision-guarded updates help preserve the intent of a request and avoid overwriting a record that has changed.
An integration people can use
The product pairs a calendar API with an MCP integration, private-file workflows and a published ChatGPT app.
03 / THE RESULT
From systems to experience.
A published ChatGPT integration backed by a private calendar product. Calendar operations manage records; social publishing is a separate workflow.
NEXT / LET’S BUILD SOMETHING