io.github.ai-aviate/better-notion
NPM · BETTER-MCP-NOTION · SCANNED SEP 20
Operate Notion with a single Markdown document — read, create, and update pages in one call.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security92
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects katex 0.12.0, reached via @tryfabric/martian > remark-math > micromark-extension-math > katex. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 80 of 175 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 212 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2282 tokens (~253/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ai-aviate/better-notion MCP server?
io.github.ai-aviate/better-notion runs locally as an npm package, launched with npx -y better-mcp-notion. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · better-mcp-notion
claude mcp add ai-aviate-better-notion -- npx -y better-mcp-notion
{
"mcpServers": {
"ai-aviate-better-notion": {
"command": "npx",
"args": [
"-y",
"better-mcp-notion"
]
}
}
} {
"servers": {
"ai-aviate-better-notion": {
"command": "npx",
"args": [
"-y",
"better-mcp-notion"
]
}
}
} codex mcp add ai-aviate-better-notion -- npx -y better-mcp-notion
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-aviate-better-notion": {
"type": "local",
"command": [
"npx",
"-y",
"better-mcp-notion"
],
"enabled": true
}
}
} openclaw mcp add ai-aviate-better-notion --command npx --arg -y --arg better-mcp-notion
mcp_servers:
ai-aviate-better-notion:
command: "npx"
args: ["-y", "better-mcp-notion"] {
"McpServers": {
"ai-aviate-better-notion": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"better-mcp-notion"
]
}
}
} assistant mcp add ai-aviate-better-notion -t stdio -c npx -a -y better-mcp-notion
{
"mcpServers": {
"ai-aviate-better-notion": {
"command": "npx",
"args": [
"-y",
"better-mcp-notion"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/better-mcp-notion@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3wc5-fcw2-2329 | CVE-2024-28246 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L | yes |
| GHSA-64fm-8hw2-v72w | CVE-2024-28243 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-cg87-wmx4-v546 | CVE-2025-23207 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-f98w-7cxr-ff2h | CVE-2024-28245 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 175 packages
| Packages resolved | 175 |
|---|---|
| Stale | 80 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
comment ~122
Add or read comments on a Notion page. ## Read comments comment({ page: "abc123" }) Returns all comments on the page as a Markdown list. ## Add a comment comment({ page: "abc123", body: "Looks good! Ready to ship." }) Adds a comment to the page. You can use the page name, ID, or URL.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Comment text to add. If omitted, existing comments are returned instead. |
| page | string | yes | Page ID, URL, or name |
No output schema declared.
No examples provided.
delete ~56
Archive (soft-delete) a Notion page. The page is moved to Trash and can be restored from Notion's UI. This does NOT permanently delete the page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Page ID or Notion URL to archive |
No output schema declared.
No examples provided.
list ~350
List database records as a Markdown table, or list child pages of a page. For databases: returns a table with properties as columns. For pages: returns a numbered list of child pages. You can pass a database/page name (resolved via search) or an ID/URL. ## Filter syntax (databases only) Simple expressions matched against DB property names and types: - "Status is Done" → select/status equals - "Priority = High" → select equals - "Tags contains backend" → multi_select contains - "Done is true" → checkbox equals - "Due Date after 2026-03-01" → date after - "Score > 80" → number greater_than - "Name contains API" → title/rich_text contains Multiple filters: separate with " AND " (e.g. "Status is Done AND Priority is High") ## Sort syntax (databases only) - "Due Date ascending" or "Due Date asc" - "Created descending" or "Created desc" ## Example output # Task Board (24 items) | Name | Status | Due Date | |---|---|---| | Fix login bug | In Progress | 2026-03-01 |
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter expression (e.g. "Status is Done", "Priority > 3"). See tool description for syntax. |
| limit | integer | – | Max items to return (default: 50) |
| sort | string | – | Sort expression (e.g. "Due Date ascending", "Created desc") |
| target | string | yes | Database or page: name (e.g. 'Task Board'), ID, or Notion URL |
No output schema declared.
No examples provided.
move ~89
Move a Notion page to a different parent page or database. The page keeps its content and properties; only the location changes. Example: move a page into an "Archive" page, or move a task into a different database.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Page ID or URL of the page to move |
| to | string | yes | Destination: page name, database name, ID, or URL |
No output schema declared.
No examples provided.
read ~261
Read a Notion page and return it as Markdown with YAML frontmatter. Returns frontmatter fields: - id, url: page identifiers - title: page title - parent / database: parent page ID or database ID - icon, cover: emoji or image URL - properties: database properties (if the page belongs to a database) - created, last_edited: timestamps (read-only) The body contains the page content as standard Markdown. The output can be edited and passed directly to the "write" tool to update the page. Use "depth" to include child pages in a single call (default: 1 = current page only, 2 = include children, 3 = include grandchildren). Example output: --- id: abc123-def456 title: Weekly Review database: task-db-id properties: Status: In Progress Tags: - backend --- ## Notes - Completed API design
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to read child pages: 1 = this page only (default), 2 = include children, 3 = include grandchildren |
| page | string | yes | Notion page URL (https://notion.so/...) or page ID (UUID or 32-char hex) |
No output schema declared.
No examples provided.
schema ~336
View or modify database schema (columns/properties). ## Actions ### "list" (default) — View current schema schema({ database: "Task Board" }) Returns: property names, types, and select/multi_select options. ### "add" — Add a new property schema({ database: "Task Board", action: "add", property: "Priority", type: "select", options: ["Low", "Medium", "High"] }) ### "remove" — Remove a property schema({ database: "Task Board", action: "remove", property: "Old Column" }) ### "rename" — Rename a property schema({ database: "Task Board", action: "rename", property: "Due", name: "Due Date" }) ## Supported types for add title, rich_text, number, select, multi_select, date, checkbox, url, email, phone_number, status, people, files For select/multi_select, you can provide initial options.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | "list" (default): show schema. "add": add property. "remove": remove property. "rename": rename property. |
| database | string | yes | Database name, ID, or URL |
| name | string | – | New name for rename action |
| options | array | – | Options for select/multi_select (e.g. ['Low', 'Medium', 'High']) |
| property | string | – | Property name (required for add/remove/rename) |
| type | string | – | Property type for add (e.g. select, number, rich_text) |
No output schema declared.
No examples provided.
search ~180
Search the Notion workspace by title keyword. Returns a Markdown list with page/database IDs, titles, and metadata. Use the returned IDs with other tools: read (to get full content), write (to update), list (to query a database), delete, or move. Example output: # Search results: "MCP" (2 results) 1. **MCP Design Doc** (📝 page) - ID: `abc123` - Last edited: 2026-02-19 2. **Task Board** (database) - ID: `def456`
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter by type: "page", "database", or "all" (default) |
| limit | integer | – | Max results (default: 10) |
| query | string | yes | Search keyword (matched against page/database titles) |
No output schema declared.
No examples provided.
update ~263
Quickly update page properties without rewriting content. Much simpler than the write tool for property-only changes. The page content (blocks) is never touched — only properties are updated. ## Parameters - page: Page ID, URL, or name - properties: Key-value object of properties to set ## Examples Update a single property: update({ page: "abc123", properties: { "Status": "Done" } }) Update multiple properties: update({ page: "My Task", properties: { "Status": "Done", "Priority": "High", "Due Date": "2026-03-01" } }) Supported value types: - Text: "value" - Number: 42 - Checkbox: true / false - Date: "2026-03-01" - Date range: "2026-03-01 to 2026-03-15" - Select/Status: "Option Name" - Multi-select: ["tag1", "tag2"] - URL: "https://..."
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Page ID, URL, or name |
| properties | object | yes | Properties to update as key-value pairs (e.g. { "Status": "Done", "Priority": "High" }) |
No output schema declared.
No examples provided.
write ~625
Create or update Notion pages from Markdown with YAML frontmatter. Mode (default "auto"): if frontmatter has "id" → update, otherwise → create. ## Batch mode Separate multiple pages with a line containing only "===" to create/update them in one call. ## Frontmatter fields | Field | Create | Update | Description | |-------|--------|--------|-------------| | id | - | required | Page ID to update | | title | recommended | optional | Page title | | parent | required* | ignored | Parent page name or ID | | database | required* | ignored | Database name or ID (*either parent or database) | | icon | optional | optional | Emoji (e.g. 📋) or image URL | | cover | optional | optional | Cover image URL | | properties | optional | optional | DB properties (see below) | Properties are auto-matched to the database schema. Use the exact property name as key. Read-only fields from read output (url, created, last_edited, formula, etc.) are safely ignored. ## Examples ### Create a page under a parent page: ``` --- title: Meeting Notes parent: "Project Alpha" icon: "📝" --- ## Agenda - Review progress ``` ### Create a database entry: ``` --- title: Fix login bug database: "Task Board" properties: Status: In Progress Tags: - backend - urgent Due Date: "2026-03-01" --- ## Description Login fails when password contains special chars. ``` ### Update an existing page (edit output from read): ``` --- id: abc123-def456 title: Updated Title properties: Status: Done --- ## New content Body replaces all existing blocks. ``` ### Append to an existing page (add content without rewriting): Use position: "append" to add content to the end, or "prepend" to add to the beginning. Only the new content needs to be provided — existing content is preserved. ``` --- id: abc123-def456 --- ## New section added at the end ``` ### Batch create (multiple pages in one call): ``` --- title: Task 1 database: "Task Board" properties: Status: Todo --- Task 1 details === --- title: Task…
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | Markdown with YAML frontmatter. Separate multiple pages with '===' on its own line. See tool description for format. |
| mode | string | – | "auto" (default): create if no id, update if id present. "create": force create. "update": force update (requires id). |
| position | string | – | "replace" (default): replace all content. "append": add to end (efficient, no need to send existing content). "prepend": add to beginning. Only affects updates. |
No output schema declared.
No examples provided.
What is the io.github.ai-aviate/better-notion MCP server?
io.github.ai-aviate/better-notion is an MCP server listed in the public MCP registry as io.github.ai-aviate/better-notion. Operate Notion with a single Markdown document, read, create, and update pages in one call. This page covers its npm package (better-mcp-notion).
Is the io.github.ai-aviate/better-notion MCP server safe to use?
io.github.ai-aviate/better-notion scores 76 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ai-aviate/better-notion MCP server expose?
io.github.ai-aviate/better-notion exposes 9 tools: read, write, search, list, delete, and 4 more. Their descriptions and schemas cost roughly 2,282 tokens of context every time the server is loaded.
Is the io.github.ai-aviate/better-notion MCP server still maintained?
io.github.ai-aviate/better-notion is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ai-aviate/better-notion MCP server under?
io.github.ai-aviate/better-notion declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.