Automic VaultAutomic Vault

brew

Install notion-mcp-server with Homebrew

MCP Server for Notion. Version 2.4.1 via Homebrew; verified 2026-06-23.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install notion-mcp-server

local Homebrew formula metadata

overview

Package summary

MCP Server for Notion

Commands and aliases

  • notion-mcp-server

history

Project history and usage

The local Notion MCP server is Notion's official package for exposing the Notion API through the Model Context Protocol. The GitHub repository was created on 2025-03-10, the npm package @notionhq/notion-mcp-server was first published on 2025-04-03, and Homebrew packages the same tool as notion-mcp-server.

The package occupies a transitional spot in Notion's AI-tooling story. Notion's developer docs now emphasize the hosted Notion MCP service at https://mcp.notion.com/mcp, while the local server README says active support is prioritized for the remote service and notes that the local repository may be sunset.

Project history

The server started as a local MCP wrapper around the Notion API. Its README documents installation through npx, Docker, and MCP client JSON config, with NOTION_TOKEN or OPENAPI_MCP_HEADERS used to pass Notion credentials.

Version 2.0.0 moved the local server to the Notion API 2025-09-03 surface, replacing database-oriented tools with data-source-oriented tools. Later README text also documents Markdown-oriented page tools tied to the Notion API 2026-03-11 operation version.

Adoption history

Adoption was driven by the 2025-2026 MCP wave rather than by older Notion API automation. The repository had 4,473 GitHub stars and 589 forks when queried on 2026-07-01, and npm reported 2,135,387 downloads for @notionhq/notion-mcp-server from 2025-06-29 through 2026-06-28.

Homebrew's formula API reported 453 install-on-request events over its 365-day analytics window. That is small next to npm usage, which matches the package's main distribution path: MCP clients usually run it through npx or Docker rather than as a long-lived Homebrew CLI.

How it is used

Package users add the server to MCP-capable tools such as Claude Desktop, Cursor, Zed, GitHub Copilot CLI, or similar clients, then provide a Notion integration token. Practical use is agent access to Notion pages and databases/data sources: searching workspace content, reading page content, creating comments or pages, and editing page Markdown.

Notion's hosted MCP documentation recommends OAuth against https://mcp.notion.com/mcp for many clients. Package nerds should treat the Homebrew formula as a convenience for local/offline or pinned-tool workflows, not as the primary future-facing Notion integration path.

Why package nerds care

This is a good example of a vendor-owned MCP package being overtaken by a hosted MCP endpoint. The package is still useful for reproducible local toolchains, but the official docs now steer users toward a remote, OAuth-backed server.

Timeline

  • 2025-03-10: GitHub repository created.
  • 2025-04-03: npm package @notionhq/notion-mcp-server created.
  • 2026-01-31: GitHub release v2.1.0 published.
  • 2026-06-22: npm package modified to version 2.4.1.

Related projects

  • Notion MCP hosted service
  • Notion API
  • Model Context Protocol
  • claude-code-notion-plugin

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:server

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Unix
.cursor/mcp.json~/.copilot/mcp-config.json

Credential files

Credential-bearing paths to review before unattended agent runs.

macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Unix
.cursor/mcp.json~/.copilot/mcp-config.json

executables

Installed executables

CommandKindExposureNote
notion-mcp-servercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version2.4.1
manager updated2026-06-23
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/makenotion/notion-mcp-server

install metadata

Package metadata

Package keybrew:notion-mcp-server
Version2.4.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/notion-mcp-server
Homepagehttps://github.com/makenotion/notion-mcp-server
Repositoryhttps://github.com/makenotion/notion-mcp-server
Upstream docshttps://developers.notion.com/docs/get-started-with-mcp
LicenseMIT
Source archivehttps://registry.npmjs.org/@notionhq/notion-mcp-server/-/notion-mcp-server-2.4.1.tgz
Last updated2026-06-23T21:55:45Z
Pulseupdated
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namenotion-mcp-server
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment