append-block-children
Append blocks to a parent block
LABSCO SUMMARY
Reading and writing Notion come from the same short tool list.
The set is close to symmetric: database, page and block can each be read and changed, and archiving stands in for deletion on pages and blocks. Reach is decided outside the server, so whatever the integration has been granted is exactly what search and list-databases will see. Paging is explicit on the query, children and search calls, which means large collections arrive a cursor at a time.
What it is
A Notion server covering the database, page and block layers of the API, with workspace search on top.
What you get
- Database work: list what the integration can reach, query one by ID with filters, sorts and cursor paging, create a database under a parent page, and change an existing one's title, description or property schema.
- Page work: create a page in a database with its properties and initial children, fetch a page by ID, and update its properties or archive it.
- Block work: read a block, list a block's children with paging, append children to a block, and change a block's content or archive status.
- Search across pages and databases with a filter, a sort and paging.
Requirements
A Notion integration with the databases and pages you want reachable shared with it — list-databases returns only what that integration has been granted.
Setup effort
One command plus a key — npx -y @sjotie/notion-mcp-server, then supply credentials
USE CASES
01
Finding the page you half-remember writing
Search on whatever phrase you recall, open the page that looks right, and read its blocks to confirm it.
02
Filing a structured record in the right database
See which databases are reachable, query one to learn what its rows look like, then add the new entry with its properties filled in.
03
Updating a tracker row after something changed
Query the database for the row that matches, then set the properties that moved — or archive the row if the work is over.
04
Standing up a new tracker and its columns
Create the database under a parent page with its property schema, adjust the schema once the shape settles, and seed the first row.
05
Editing the body of a page that already exists
Walk the block tree, add new blocks at the right point, and rewrite or archive the ones that no longer hold.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create-database
Create a new database
create-page
Create a new page in a database
get-block
Retrieve a block by its ID
get-block-children
Retrieve the children blocks of a block
get-page
Retrieve a page by its ID
list-databases
List all databases the integration has access to
query-database
Query a database
search
Search Notion for pages or databases
update-block
Update a block's content or archive status
update-database
Update an existing database
update-page
Update an existing page
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. The integration sees nothing until someone adds it to each page or database through Add connections, so an empty list-databases usually means nothing has been shared yet.
Requires
- npx on PATH
- NOTION_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"@sjotie/notion-mcp-server"
]
}
}
}The configuration on this page does not set NOTION_API_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
npx
TERMINAL
npx -y @sjotie/notion-mcp-server
