Notion has a first-party MCP server, which makes it one of the two apps in this cluster where you are not choosing between community projects. The setup question that trips almost everyone is not technical: Notion's permission model means a correctly configured connection starts with access to absolutely nothing.
"It connected but it cannot find my pages"
That is the expected first state. Notion connections see only what has been explicitly shared with them. Share the top-level page or database you want reachable and the children come along; share nothing and the assistant will truthfully report an empty workspace. Share deliberately rather than sharing everything, because whatever you share becomes readable by whatever you say next.
Blocks are why editing feels clumsy
Notion pages are trees of typed blocks, not documents. Appending is reliable. Editing something in the middle of a rich page means reading the tree, identifying the block, and replacing it — and a server that gets this slightly wrong produces a page that looks subtly wrong in ways you notice a week later. Append freely; edit surgically.
Databases are where it earns its keep
Querying a Notion database in natural language is genuinely faster than building a view, and creating rows with correctly typed properties is the intake win. Get the property vocabulary right first: select options must match exactly, and relations need a real page reference.
Where LemTask stands today
LemTask does not ship an MCP server yet, and we are not going to pretend otherwise on a page developers will read. What LemTask has working right now is outbound and inbound webhooks, Zapier, Make and Apple Shortcuts, which covers "when a task is created, do X" and "create a task from anything that can send an HTTP request". An MCP connection is on the roadmap; when it ships and we have tested it end to end with Claude, this page will say so with the config block, and not a day earlier.