Item detail
github.com

FR0ZON3/notion-mcp

RepoRadar surfaced FR0ZON3/notion-mcp — a notion mcp server (42 tools, mar — into the MCP Servers section, where it sits at Silver tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.0 out of 10.

Score7.5
Popularity1.0
Riskconditional
TierSilver
Score breakdown
Usefulness8.0
Novelty7.0
Momentum7.0
Maturity5.5
Open-source/build8.4
Evidence7.2
Workflow potential9.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for AI coding agents and humans who want to drive Notion from Claude Code / Cursor / Claude Desktop without ever constructing raw Notion block JSON — agents edit standard GFM, the server handles block conversion, database schema mapping, and OAuth, and the markdown round-trip is bidirectional (what you read in the chat is what the page actually contains). 42 MCP tools cover the common Notio

Who should use it

AI coding agents (Claude Code, Cursor, Claude Desktop) that need to read and write Notion pages and databases without constructing raw Notion block JSON — the agent talks in standard GFM, the server handles block conversion and database schema mapping, and the round-trip is bidirectional (what the agent sees in the chat is what the page contains after the write)Claude Code workflows that need to update Notion databases from an agent without the agent first learning the schema — write `{Status: Done}` and the server infers the right property type, which is the durable differentiator for any task pipeline that has to mark tickets / projects / status fields from an automated agentTeams running multiple MCP server instances behind a load balancer who need shared schema cache and OAuth token persistence — drop in Redis and the server becomes multi-instance safe, with single-instance still working without Redis as a graceful fallbackAnyone who needs to drive Notion from a non-Claude-Code MCP client (HTTP transport) with OAuth or a bearer-protected static token — the same server, the same 42 tools, the same security defaults, but reachable over HTTP for cloud clientsSecurity-sensitive teams who want hardened defaults (content-notice prefix, URL sanitization, workspace-root file containment for the easy-notion CLI) and not 'paste your integration token and hope'Power users who want a low-context CLI (`easy-notion`) with readonly / readwrite profiles for direct terminal use without the agent loop — useful for scripted page management and quick edits

Who should skip it

Pass on FR0ZON3/notion-mcp if its scope or audience does not match what your team is building right now.

About this signal

FR0ZON3/notion-mcp is tracked by RepoRadar as a notion mcp server (42 tools, mar in the MCP Servers section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, FR0ZON3/notion-mcp is strongest on workflow potential (9.0) and open-source/build quality (8.4) and weakest on maturity (5.5) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned FR0ZON3/notion-mcp a composite score of 7.5 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

Conditional risk: review permissions, runtime environment, and data boundaries before production use.

Evidence links
Closest alternatives / related signals
mcpmcp-servernotionmarkdowngfmoauthredisclaude-code