Your library is a tool
Notebooker speaks MCP. Point Claude, Cursor or anything else that speaks it at one URL, sign in once, and it can read what you saved and build from it.
Eleven tools, one URL
These are the same tools Notebooker’s own agent calls when it works inside a notebook. There is no second, thinner API for outside clients. The catalog is shared, so anything the app can do to your library, your AI client can do too.
- manage_notebookslist, create, update
- manage_sourcesadd a link or text, check status
- searchfull-text across your library
- askgrounded answer with citations
- chatnotebook conversation
- manage_creationsgenerate, edit source, publish
- manage_podcastsgenerate and publish
- transformationsrun a saved prompt
- insightsper-source summaries
- podcast_profilesspeakers and episode settings
- manage_notescreate, edit and delete notes
Sign in once. No keys to paste.
Connecting uses OAuth with dynamic client registration, so a client that supports MCP can register itself. You approve it in the browser and revoke it the same way.
Add it as a custom connector in settings, then approve the sign-in.
Add the URL to your MCP config and the editor handles the handshake.
Connect it as a custom MCP server from the connector settings.
Use the MCP node, or drive the REST API with a personal key.
Any MCP client can connect. Nothing about the server is specific to one of them.
If you would rather use plain HTTP, the same operations are a documented REST API.
What a connected client can and cannot do
It acts as your account and sees only your library.
Generating something spends against the same budget the app uses. Set it to zero and nothing costs.
Disconnect a client and its access ends immediately.
It cannot change billing, read another tenant, or reach your provider keys.