For people who keep a notebook
A notebook that you actually own.
Sign in with Google, write notes in a block editor, organise them with tags, and let your AI tools read and write them too. Your notes live in your database, your account is your Google identity, and nothing here is built to keep you scrolling.
What it does for you
Most notebooks are a list of files. This one is a list of notes — titled, searchable, organised by tags — that you and your AI clients can both reach. Here is what each part is for.
Sign-in
One click with Google. No new password, no email confirmation, no profile to fill out. Your account is your Google identity, and the rest of the app treats you as that identity from then on.
Block editor
Each note is one document. You write in paragraphs, headings, bullet lists, numbered lists, code blocks, quotes, and dividers. Press / to switch block types. There is no rich-text toolbar to learn — the keyboard and the slash menu cover it.
Tags
Flat labels. A tag is a word you attach to notes so you can group them. One tag on a hundred notes, ten tags on one note. There is no hierarchy, no nesting, no smart folders. If you want to group, you make a tag.
Full-text search
Every word you wrote is searchable. The search runs against an index of the plain text in your notes, so it finds what you remember writing, not just what the headings say.
API keys
You can generate API keys from the settings page. Each key has a name you choose (e.g. “Claude Desktop”), a scope of read-only or read-write, and a prefix you can recognise in the UI. You can revoke any key at any time. The raw key is shown once at creation and never again.
MCP server
The same API keys above work with an MCP server that ships with this app. Plug a key into Claude Desktop or Cursor and your notes become tools that your AI client can call: list notes, read a note, create a note, update a note, delete a note, list tags, list notes by tag. Your AI talks to your notes directly. No copy-paste round trip.
What is not here, by design
A list of features you will not find, and a reason for each, so you can decide whether the absence is fine or a deal-breaker.
No teams, no shared notes
This is one person, one account. There are no workspaces, no collaborators, no permission systems, no share links. If you want to send a note to someone, you copy the text out and paste it somewhere else.
No mobile app
There is no iOS or Android app. The web app works in a mobile browser. If you need a native app on your phone today, this app will frustrate you.
No offline mode
If you have no connection, you cannot open the editor. The app does not cache your notes on the device.
No attachments, no image uploads
Notes are text. You can paste images into the editor in the way the block editor supports, but there is no first-class file hosting, no PDF storage, no audio.
No versioning, no history
When you save a note, the previous version is replaced. There is no “view edits”, no diff, no undo beyond the editor’s own undo while you are typing.
No light mode
The interface is dark only. There is no toggle. This is not a roadmap item; it is a design choice.
No engagement features
There are no notifications, no comment threads, no “daily streak”, no recommendations, no social graph, no suggested tags, no AI summarising your notes to show you a digest. The app does not try to bring you back. It is a tool, not a feed.
How your data works
You should be able to answer these questions before you put anything personal in.
Where are my notes stored?
In a Postgres database hosted on Neon. The web app reads and writes through a typed schema. The MCP server reads and writes through the same schema. There is one source of truth.
How does sign-in work?
Firebase Authentication verifies your Google account. Firebase issues a session cookie that the web app verifies on every server-rendered page and every server action. Sign-out clears the cookie and revokes the underlying refresh tokens.
How are API keys protected?
Each raw key is generated once, shown once, and then stored only as a bcrypt hash. The prefix (the first few characters) is kept in plain text so you can recognise a key in the UI. Verification recomputes the hash and compares. There is no way to recover a raw key after creation.
Is anything I write used to train a model?
No. The block editor is yours. The MCP server forwards your notes to your AI client and your AI client’s response back to your notes — those calls go through Anthropic or OpenAI or whoever your client is configured to use, and they happen inside your client, not here. Nothing you write is sent to this app’s author.
Can I leave?
Yes. Export your notes as JSON from the settings page. Delete your account from the settings page. Account deletion removes your user, your notes, your tags, your note–tag links, and your API keys. There is no archive, no soft delete, no 30-day recovery window.
What is not finished yet
This is an early version. The auth flow and the dashboard shell are done. The following things are planned but not shipped:
- Creating, editing, and deleting notes inside the editor.
- A non-empty notes list page, including search and tag filtering.
- API key management from the settings page.
- The MCP server itself (the keys work, the server is next).
- Mobile and offline support.
- Light mode (if ever).
If any of those are blockers for you, this app is not ready for you yet, and you should use something else. If you are fine waiting for them, sign in.
That is the whole pitch.
No testimonials, no usage stats, no “trusted by”, no comparison table against other apps. You sign in, you write, you leave when you want to.