MCP server

Let an agent author pages

OpenBook speaks the Model Context Protocol, so an MCP-capable assistant can read, create and edit your documents directly — building the reactive tools it would otherwise hand-code.

The tool surface

The server exposes a small set of tools over MCP; edits apply through the CRDT path, so an agent and a human can work the same document at once.

text

# Tools the MCP server exposes to an agent:

# Pages
list_pages
read_page               { pageId }
search_notes            { query }
create_page             { title, content }
create_artifact_page    { title, blocks }        # a reactive tool page
append_to_page          { pageId, content }
inspect_page_structure  { pageId }               # block ids + types

# Reactive blocks (edits apply through the CRDT path)
append_blocks           { pageId, type, text }
update_block            { pageId, blockId, text }
get_kit_values          { pageId }
set_kit_value           { pageId, name, value }

# Databases
list_database_rows      { pageId }
create_database_row     { pageId, properties }
list_db_views           { pageId }
get_db_row              { pageId, rowId }
set_db_cell             { pageId, rowId, propertyId, value }

Why it matters

Because pages can hold live inputs, formulas and charts, “write me a calculator” becomes a real, editable artifact instead of a screenshot. The agent assembles blocks; you keep editing them.