fridge-notes through Meradomo, then connects to it from a
separate client with remote-notes-client.
Prerequisites
- Meradomo installed and connected — the menu-bar app shows a green dot. (Get Meradomo.)
- Node.js ≥ 20 on your Mac.
- The two sample apps from this repo (
examples/fridge-notes,examples/remote-notes-client).
1
Publish Fridge Notes (~3 min)
Start the sample app:It starts on a random local port and immediately requests publication:
2
Approve in the menu-bar app
A prompt appears in the Meradomo menu-bar app:
Fridge Notes wants to be available through your Meradomo.Click Allow.
3
Open your live address
The terminal prints something like:Open it in a browser. Sign in with your Meradomo account if prompted (once). You’ll see the notes
page greeting you: “Hello, you@email.com” — the app never handled sign-in; it just read the
X-Meradomo-Email header Meradomo injected.4
Connect a remote client (~5 min)
To use the Connect path you need an OAuth client for your app.Run the sample client with your credentials:
Self-serve client registration is coming to the developer portal. For now,
request an OAuth client and you’ll receive a
clientId and, for
confidential clients, a clientSecret.5
Approve in the browser
The script prints an authorization URL. Open it, sign in, and click Allow on the consent page
(“Remote Notes wants to connect to your Meradomo”). The browser redirects back to the client’s
local callback, and the script prints the notes list it fetched with the access token.
What just happened
- fridge-notes used the local management API to register itself — no SDK or library.
- remote-notes-client ran the full OAuth 2.0 + PKCE flow to obtain an access token the Meradomo agent validates on every request.
- The agent injected the verified
X-Meradomo-Emailheader so the app could greet you without ever handling sign-in.
Next steps
Agent API
Publish lifecycle + identity headers.
Connect (OAuth)
Endpoints, token claims, revocation.
Security model
What your app can trust.