ClawHosters
by Daniel Samer
5 min read
Your AI agent knows a lot about the world. But it knows nothing about your project board, your meeting notes, or that CRM database you built in Notion last Tuesday. The Notion MCP server fixes that.
Once connected, your OpenClaw agent can search your workspace, read pages, create new entries, update properties, and query databases with filters. It becomes a Notion assistant that actually understands your data, not just generic productivity advice.
What You Need Before Starting
Two things. A Notion account with at least one workspace, and an OpenClaw instance on the Balanced or Pro tier (MCP connections require these tiers). The Budget tier doesn't support custom MCP servers.
You don't need a terminal or command line experience. On ClawHosters, the config happens through the dashboard or a simple SSH edit. If you've ever edited a text file, you can do this.
Step 1: Create a Notion Integration
Go to notion.so/my-integrations and click "New integration." Give it a name like "OpenClaw Agent" and select your workspace. The integration type should be "Internal."
After creation, you'll see an API token starting with ntn_. Copy it. You'll need it in Step 3.
Quick note on permissions: the default settings (Read, Update, Insert content) work fine for most use cases. You probably don't need the "Delete content" capability unless you're building something specific.
Step 2: Share Pages With Your Integration
This is the step people skip, and then wonder why everything returns 404 errors.
Notion integrations can only access pages you explicitly share with them. Open the page or database you want your agent to read, click the three-dot menu in the top right, scroll to "Connections," and add your integration by name.
You need to do this for every top-level page you want accessible. Child pages inherit the connection from their parent, so sharing a parent page covers everything nested under it.
Step 3: Add the MCP Server Config
On your ClawHosters instance, add this block to your openclaw.json under mcpServers:
{
"notionApi": {
"command": "npx",
"args": ["-y", "@notionhq/notion-mcp-server"],
"env": {
"NOTION_TOKEN": "ntn_your_token_here"
}
}
}
The @notionhq/notion-mcp-server package is the official Notion MCP implementation, maintained by the Notion team. It's also on the ClawHosters verified package list, so you won't run into compatibility issues.
After saving, restart your gateway. The server takes about 10 seconds to spin up.
For the full config walkthrough, the MCP Servers Guide covers the general process in more detail.
What Your Agent Can Actually Do
The official Notion MCP server exposes 22 tools. Here are the ones you'll use most:
Search your entire workspace by keyword
Read pages and all their nested block content
Create new pages with custom properties
Query databases with filters and sorting (like a Notion formula, but in natural language)
Update page properties like status, assignees, and dates
Add comments to existing pages
In practice, you can say "show me all tasks assigned to me that are due this week" and get a filtered database query back. Or "create a meeting notes page for today's standup with these action items" and it builds the page with the right template.
Practical Use Cases
Morning briefing: Ask your agent to summarize what's overdue in your task database and what meetings are scheduled today. It pulls live data, not guesses.
Research assistant: Tell it to save findings to a specific Notion page as you work. Every answer gets appended as a content block with the source.
CRM updates: After a client call, tell your agent to update the contact's status, add notes, and set the next follow-up date. All in one message.
Knowledge base queries: "What did we decide about the pricing model in last week's meeting?" Your agent searches your meeting notes and finds the answer.
Limitations Worth Knowing
The Notion MCP server has a few constraints. The API enforces a 3 requests/second rate limit, so bulk operations take time. Rich text blocks are capped at 2,000 characters each. File attachments and media aren't accessible through the API. Synced blocks and transcription blocks don't work either.
The biggest practical limitation is the manual page sharing from Step 2. There's no "share everything" toggle. If you forget to share a page, your agent simply can't see it. This is a security feature, but it catches people off guard.
RAM usage stays reasonable. Node.js MCP servers typically use 50 to 150 MB, which fits comfortably on all ClawHosters tiers. Check the docs for resource monitoring details.
