A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Notion is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
16
downloads a day
local
runs on your machine
344
downloads in 30d
What it does
Search, read and write your Notion workspaces, with pages as Markdown and typed database queries.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'NOTION_TOKENS_DIR=${NOTION_TOKENS_DIR}' --transport stdio foreverworks-notion-mcp '--' npx -y @foreverworks/mcp-notion
# 2 — ask your agent for something these tools do
# list_accounts, health, list_users and 24 more
It needs NOTION_TOKENS_DIR: this reads it from your environment, so export it first.
Notion costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FOAll 6 servers
foreverworks6 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Notion as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads NOTION_TOKENS_DIR (A folder holding one file per workspace, notion-<label>, each with that workspace's integration token or personal access token) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx NOTION_TOKENS_DIR … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'NOTION_TOKENS_DIR=${NOTION_TOKENS_DIR}' --transport stdio foreverworks-notion-mcp '--' npx -y @foreverworks/mcp-notionReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: NOTION_TOKENS_DIR — A folder holding one file per workspace, notion-<label>, each with that workspace's integration token or personal access token.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
The Notion workspaces this server reaches, by label (one per token file), from the token files alone: no
No parameter schema on file.
Ask each workspace: is its integration token accepted, which workspace and integration it is, and whether it
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | yes | — |
The people (and bots) of every workspace, or of the one account names: each one's id, name, and email when the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words in a name or an email. Leave it out to list everyone. |
| account | yes | — |
Pages and databases by title, in every workspace at once unless account names one. Notion matches words in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words in the title. Leave it out to list everything, newest edit first. |
| kind | string | no | Only pages, or only databases. |
| account | yes | — | |
| limit | integer | no | Hits per workspace; across several workspaces, up to this many from each. |
| cursor | yes | — |
The blocks directly inside a page or a block, in order, one level down: each one's id, type and plain text,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block | string | yes | The page or block: its id, or a Notion URL. A URL's #fragment names a block inside the page, and that block is the one read. |
| limit | integer | no | Blocks to return; more than 100 are read 100 at a time. |
| cursor | yes | — | |
| account | yes | — |
The open comments on a page, oldest first, each with its discussion, author, time and text. Resolved ones are not listed by Notion.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| limit | integer | no | Comments per call. |
| cursor | yes | — | |
| account | yes | — |
A comment on a page, or a reply in one of its discussions, shown in Notion as the workspace's integration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| markdown | string | yes | The comment, in Markdown. |
| discussion | string | no | A discussionId from get_comments, to reply in that thread. Default: a new comment on the page. |
| account | yes | — |
Markdown added to a page's body: at the end (default), at the start, or after a passage. Not resent after a lost answer: that is outcome_unknown, and read_page says whether it went through.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| markdown | string | yes | — |
| at | string | no | Where it goes. |
| after | string | no | Or after a passage, named "first words...last words" as it reads in the page. |
| account | yes | — |
Find and replace in a page's body, in its Markdown as read_page shows it. The smallest change that does the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| edits | array | yes | Find-and-replace pairs, applied in order. |
| allow_deleting | boolean | no | Let the change remove child pages or databases inside the page. Off, Notion refuses such a change. |
| account | yes | — |
A page's whole body, replaced by this Markdown. Properties are untouched. Child pages and databases in the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| markdown | string | yes | Notion's Markdown: headings, lists, to-dos (- [ ]), quotes, code, tables, callouts. The page's new body; empty only with clear. |
| clear | boolean | no | Empty the body on purpose, with markdown "". Without it an empty markdown is refused, since it would erase the page. |
| allow_deleting | boolean | no | Let the change remove child pages or databases inside the page. Off, Notion refuses such a change. |
| account | yes | — |
The page templates of a database or data source, with their page ids, names and default flags. Use this catalog to distinguish templates from ordinary rows; search can return both. Inspect their pages before editing recurring content. Follow nextCursor when hasMore is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | yes | — | |
| source | yes | — | |
| account | yes | — | |
| cursor | yes | — | |
| limit | integer | no | — |
A database's columns: name, type, the options of a select, multi-select or status (with a status's groups),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | yes | — | |
| account | yes | — |
Rows of a database, filtered by where (checked against the columns first), sorted, with the columns asked
No parameter schema on file.
How many rows match where, and with by, how many hold each value of one column ("how many tasks per
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | yes | — | |
| source | yes | — | |
| where | yes | — | |
| match | yes | — | |
| notion_filter | yes | — | |
| by | string | no | A column to count by: rows per option, per value, per related page. |
| in_trash | yes | — | |
| account | yes | — |
Upload a file to Notion and attach it to a page: to one of a row's files columns, or as a block at the end of the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| file | object | yes | The file, up to … MiB (Notion's Free plan takes 5 MiB a file). … |
| column | string | no | A files column of the row to add it to, after the files already there. Leave it out to put it in a block at the end of the page's body. |
| name | string | no | The name Notion shows. Default: the file's own name. |
| replace | boolean | no | With column: drop the column's Notion-hosted files, which the API cannot write back. Its external links are always kept. |
| account | yes | — |
Save the files Notion hosts for a page to this server's outbox: its files columns and the file blocks of its body
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| column | string | no | Only this files column; the body is then left alone. |
| body | boolean | no | Also the files in the page's body: file, image, PDF, video and audio blocks, nested ones included. |
| save_dir | string | no | A folder inside the outbox, e.g. "2026-10/contracts". Default: a folder named after the page's id. |
| account | yes | — |
One page by id or URL, in whichever workspace has it: its title, parent and properties as plain values
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| content | boolean | no | Include the body as Markdown. false reads the properties alone, which is cheaper. |
| include_transcript | boolean | no | For a meeting-notes page, include the transcript. |
| account | yes | — |
A new row in a database, its properties checked against the columns first (an unknown column or option is
No parameter schema on file.
Change a page's properties (a row's columns, checked against the database's schema; a page's title as
No parameter schema on file.
Under another page, or into a database as a row. Only within the page's own workspace: Notion cannot move a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| to | string | yes | The new parent: a page, or a database (the page becomes a row). Same workspace only. |
| source | yes | — | |
| account | yes | — |
Into Notion's trash, with everything under it. Direct deletion of database templates is refused unless allow_template is explicit. Notion keeps trash 30 days; restore_page brings it back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| allow_template | boolean | no | Explicitly allow removing a database template after checking its role in list_database_templates. |
Out of Notion's trash, back where it was. Notion's API cannot restore a page from the top level of a workspace
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| account | yes | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Notion or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.1.0 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings0 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest5d42142273027c487dd03d87ac5265b6cd420b61a70a0da7492e056df673d78a
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_accounts | no tags | |
| health | no tags | |
| list_users | no tags | |
| search | no tags | |
| read_blocks | no tags | |
| get_comments | no tags | |
| add_comment | no tags | |
| append_content | no tags | |
| edit_content | no tags | |
| replace_content | no tags | |
| list_database_templates | no tags | |
| describe_database | no tags | |
| query_database | sensitive-source | sensitive-source: keyword "query database" |
| count_rows | no tags | |
| upload_file | external-sink | external-sink: keyword "upload_file" |
| download_files | untrusted-input | untrusted-input: keyword "download" |
| read_page | no tags | |
| create_page | no tags | |
| update_page | no tags | |
| move_page | no tags | |
| trash_page | no tags | |
| restore_page | no tags | |
| add_column | no tags | |
| add_options | no tags | |
| create_database | no tags | |
| list_views | no tags | |
| query_view | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
download_files → query_database → upload_file
A cross-tool exfiltration chain exists: download_files → query_database → upload_file.
Supply chain and provenance
Integrityfirst-seen
Surface digest5d42142273027c48
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Notion can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.