A blog is a stack of posts in reverse date order, which is the wrong shape for anything you meant to be read in sequence. Tilnote books fix that: you gather existing notes into an ordered collection with its own page and table of contents.
The MCP connector exposes the whole flow, so your assistant can assemble one for you.
Making a book
create_book takes a title and an optional description and hands back a book ID:
Make a book called "Tilnote MCP Guide" and put my three MCP posts in it.
From there add_page_to_book attaches notes one at a time, in the order you add them. Both published posts and private drafts can go in — a book is a container, not a publishing action.
Reading one back
get_book returns the book with its full table of contents, so the assistant can see what is already inside before adding more. That matters when you are building a book across several conversations and do not remember where you left off.
list_books gives you the shelf: every book with its page count and URL.
Rearranging
remove_page_from_book detaches a note without deleting it. The note itself is untouched — it stays in your workspace and stays published if it was published. Only the membership in the book goes away.
This is worth stating plainly because the naming invites the wrong assumption: removing a page from a book is not a delete. If you actually want the note gone, that is delete_note, and it asks for confirmation first.
A workflow that holds up
The pattern that works best is to write first and organize later:
Publish posts as you finish them, without worrying about structure
Once a few cluster around one topic, make a book
Add them in reading order rather than the order you wrote them
Books are cheap to make and easy to rearrange, so there is no cost to guessing wrong the first time. The posts stay independently readable either way — being in a book does not hide a post from your blog.
이 노트는 보도·비평·교육·연구 목적으로 작성되었습니다. 저작권 문의가 있으시면 에서 알려주세요.