Notion Arena

io.github.imgulPublished by GitHub account imgulv0.2.2Updated Oct 26, 2026

MCP server for Notion Arena — 143 Notion components: 132 widgets + 11 recipes

The publisher's own server: Notion

Overview

AI-generated overview

Local MCP server for the Notion Arena component registry, letting an assistant search, inspect and plan installation of Notion widgets and recipes.

What you can do
  • Browse and search the Notion Arena catalog of widgets and native recipes, and read categories and site info
  • Inspect a single component or registry item, including a widget's configuration schema and parameters
  • Build embed URLs for hosted widgets with chosen configuration options
  • Plan an install of a native recipe, and fetch install guides explaining the delivery channels
  • Filter components by capability flags such as offline-safe, persists locally or writes to Notion
When to use it
Useful when you want an assistant to find a suitable Notion widget or recipe and explain how to add it to a page, for example a pomodoro timer, a habit tracker or a CRM pipeline. It is a catalog and planning aid, not a tool that edits your Notion workspace itself.
Requirements
Runs locally over stdio via npx from the npm package notion-arena-mcp, so Node.js is needed. No authentication, environment variables or headers are declared. Network access is needed to fetch the package and to reach the hosted registry and embed URLs.
Before you install
The server itself plans installs rather than performing them; actually installing a native recipe requires a Notion integration token and a parent page ID, which grants write access to your workspace. Review the plan before authorizing any write. Widgets keep personal state only in the browser and cannot read or write Notion data.

Installation

In SourceWeft

  1. Open Notion Arena in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Deploy with Vercel] [npm version] [MCP Registry] [License: MIT] [PRs Welcome] [Discord]

Notion Arena

[Notion Arena Hero]

The component registry for Notion.
shadcn/ui's model: browse, configure, copy, own, install from code — applied to Notion dashboards.

[192 Widgets] [11 Recipes] [MCP Ready] [Skill Enabled]

[Time] [Dashboards] [Trackers] [Planning] [Business] [Docs] [Visuals] [Automations]


🎯 What is Notion Arena?

Notion Arena is a machine-readable component registry for Notion — 203 pre-built components you can drop into any Notion page:

192 Widgets (Embed + HTML Block)11 Native Recipes (Notion API)
WhatSelf-contained HTML files that run inside NotionDatabase schemas, views, formulas, automations installed via API
Delivery<iframe> embed or upload HTML filePOST /api/install with your token
NetworkRequired (embed) / None (HTML block)None at runtime
DataBrowser-local onlyLives in your Notion workspace
Team sync❌ No✅ Yes
UpdatesAuto (embed) / Manual (HTML)Re-run install
Min planFreeFree / Plus / Business

Notion is a trademark of Notion Labs Inc. This is an independent project and is not affiliated with or endorsed by Notion.


🎨 Popular Widgets Showcase

[Popular Widgets]

WidgetCategoryDescription
[Image] Pomodoro Timer[Image] TimeWork/break cycles with progress ring, session counter, chime
[Image] KPI Strip[Image] Dashboards4 metric tiles with sparklines, deltas, target rings
[Image] Habit Grid[Image] TrackersGitHub-style heatmap, streaks, 5-level intensity
[Image] Flip Clock[Image] DashboardsSplit-flap clock, timezone, 12/24h, Notion typography
[Image] Meeting Notes OS[Image] DocsTemplate with agenda, notes, decisions, action items
Goal Ring[Image] DashboardsSingle-metric hero with milestones & progress ring
📦 All 192 Widgets (click to expand)
CategoryCountExamples
[Image] Time12Pomodoro, Breathing, Stopwatch, Countdown, Month Calendar, Date Calculator, Flip Clock, World Clock, Count-Up, Interval Timer, White Noise, Sunrise/Sunset, Sleep Duration, Family Calendar, Study Session Log, Daily Planner, Routine Checklist, Workout Tracker
[Image] Dashboards9KPI Strip, Goal Ring, Year Progress, Moon Phase, Flip Clock, World Clock, Weekly Status Report, Sunrise/Sunset, Count-Up, Countdown, Month Calendar, Date Calculator, Stopwatch, Breathing Timer
[Image] Trackers26Habit Grid, Water Tracker, Mood Tracker, Routine Checklist, Workout Tracker, Sleep Duration, Plant Care Log, Pet Care Checklist, Volunteer Hours Log, Media Watchlist, Reading Progress, Savings Goal, Net Worth Snapshot, Expense Tracker, Portfolio Tracker, Debt Payoff Tracker, Subscription Tracker, Billable Time Tracker, Attendance Register, Collection Catalog, Gear Database, Household Inventory Log, Car Maintenance and Trip Log, Warranty and Service Log, Game Collection Catalog, Wish List and Collector Log, Healthcare Supply Inventory, Family Contacts Directory
[Image] Planning37Mini Kanban, Eisenhower Matrix, Gantt Timeline, Weekly Planner, Trip Itinerary, Meal Planner, Grocery List, Packing List, Chore Checklist, Home Maintenance Log, Product Roadmap, Sprint Retrospective, User Story Map, OKR Weekly Check-in, Daily Planner, Wedding Seating Planner, Event Run of Show, Milestone Tracker, Incident Log, QA Test Run Log, Event Guest List, Travel Itinerary Planner
[Image] Business53ROI Calculator, Budget Planner, Inventory Tracker, Local Intake Form, Ticket Queue, Asset Checkout, Subscription Tracker, Bill Splitter, Currency Converter, Quote Builder, CRM Pipeline, Sprint Tracker, Invoice Generator, Client Onboarding Tracker, Sales Follow-up Queue, Campaign Planner, Interview Scorecard, Pricing Tier Calculator, Customer QBR Prep, Freelancer Proposal Tracker, Fundraising Outreach Tracker, Vendor Register, Access Review Log, Invoice Status Tracker, Leave and Time-Off Log, Renewal Board, Escalation Tracker, Purchase Request Tracker, Equipment Inventory Log, Approvals Request Log, Helpdesk Intake Log, Editorial Calendar, Site Diary, Restaurant Reservation Log, Donor Relationship Log, Discovery Call Pipeline, Property Listing Catalog, Property Showing Schedule, Tenant and Lease Log, Manufacturing Work Order Tracker, Shipment and Logistics Tracker, Wedding Vendor Directory
[Image] Docs50Citation Builder, Reading Tracker, Spaced Repetition, Flashcards, Vocabulary Trainer, Bookmark Library, Reading List, Assignment Tracker, Exam Planner, Research Log, Protocol Checklist, Idea Inbox, Manuscript Progress, Chapter Outliner, Character Bible, Submission Tracker, Podcast Episode Planner, Guest Prep Sheet, Episode Production Checklist, Lesson Plan Builder, Research Conference Planner, Changelog Builder, SEO Content Planner, Content Repurposing Tracker, Usability Findings Log, Scholarship Tracker, Podcast Show Notes Log, Listener Feedback Log, Recipe and Meal Library, Class Homepage, Parent Communication Log, Tutoring Session Log, Research Question Log, Lab Equipment and Sample Log, Student Course Dashboard, Dissertation Milestones Tracker, Impact and Outcomes Log, Board Meeting Notes, Therapist Session Administration, Healthcare Staff Training Log, Travel Journal, Review and Rating Log, Travel Journal, Review and Rating Log
[Image] Visuals5Org Chart, Whiteboard, Quote Card, Daily Quote Card, Film Shot List, Storyboard Shot Log
[Image] Automations1Automation Starter Pack

⚙️ Native Recipes (11)

[Native Recipes]

RecipeTierCreatesPlan
CRM Pipeline[Image] Pro3 DBs, 6 formulas, 5 views, 2 templates, 3 automationsPlus
Sprint Tracker[Image] Pro2 DBs, 4 formulas, 4 views, 1 templatePlus
OKR System[Image] Free2 DBs, 5 formulas, 3 views, 1 templatePlus
Meeting Notes OS[Image] Free2 DBs, 1 template, 2 buttons, 4 views, 2 automationsFree
Content Calendar[Image] Free2 DBs, 3 formulas, 5 views, 1 recurring templatePlus
Invoice Generator[Image] Pro3 DBs, 6 formulas, 1 template, 1 button, 3 viewsPlus
PARA Life OS[Image] Pro5 DBs, 7 relations, 6 views, 3 templates, 1 dashboardPlus
Habit OS (native)[Image] Pro2 DBs, 5 formulas, 4 views, 1 button, 1 recurringPlus
Client Portal[Image] Pro3 DBs, 4 views, 1 synced block, 1 page, 2 automationsBusiness
Job Tracker[Image] Free2 DBs, 4 formulas, 4 views, 3 templatesFree
Automation Starter[Image] Free2 DBs, 12 automations, 6 buttons, 3 recurring, 4 formulasPlus

🤖 For AI Agents — MCP + Skill

Plug Notion Arena directly into your AI agent — Claude Code, Cursor, Windsurf, Claude Desktop.

MCP Server

Gives your agent tools to list/search/configure/plan-install all 203 components:

bash
# Claude Code (project scope)claude mcp add --scope project notion-arena -- npx -y notion-arena-mcp
# Or pinned versionnpx -y [email protected]
# Cursor — .cursor/mcp.json# Claude Desktop — claude_desktop_config.json# See docs/AGENT_SETUP.md for all clients

Skill

Teaches your agent the Notion Arena workflow, delivery channels, widget contract:

bash
# Via skills.sh (Vercel) — cross-agentnpx skills add SynergyFlowLabs/notion-arena --skill notion-arena
# Via Claude Code plugin marketplace/plugin marketplace add SynergyFlowLabs/notion-arena/plugin install notion-arena@notion-arena-marketplace
# Manualcp -r skills/notion-arena .claude/skills/notion-arena

Once both are installed, just ask:

"Find me a pomodoro timer for Notion" "Add a CRM pipeline to my Notion" "I need a habit tracker that works offline"

Your agent will use search_components, get_component, build_embed_url, plan_install automatically.

MCP Tools: list_components, search_components, get_component, get_widget_schema, build_embed_url, plan_install, get_registry_item, get_install_guide, get_categories, get_site_info

Skill: skills/notion-arena/SKILL.md + .claude/skills/notion-arena/SKILL.md + .claude-plugin/plugin.json + .claude-plugin/marketplace.json

[MCP Flow]

See docs/AGENT_SETUP.md for MCP+Skill setup and docs/DEPLOY_AND_PUBLISH.md for free deployment (Vercel) + publishing MCP to npm & registry and Skill to skills.sh & plugin marketplace.


🏗️ Three Delivery Channels — Visualized

[Delivery Channels]

Embed URLHTML BlockNative Recipe
What it isWe host the widget, Notion iframes itYou upload the file to Notion's storageWe call the Notion API
Install/embed → paste/html → upload, or 3 API callsPOST /api/install
Network at renderRequiredNoneNone
Reads your Notion dataNoNoIt is the data
State shared with teamNoNoYes
Gets our updatesAutomaticallyNo. Frozenn/a
Min. planFreeFreeFree

One HTML file serves both widget channels, so they cannot drift. Configuration comes from the query string on the hosted path and from a baked-in <script id="bk-config"> on the downloaded path, because a sandboxed block has no URL.


📋 Widget Contract — The 4 Rules

Every widget in public/widgets/ implements the same four rules. See /docs/authoring for the full guide and checklist.

[Widget Architecture]

RuleDescription
1. Zero External RequestsNo CDN, no webfont, no fetch(), no @import. The sandbox has no network — a remote asset is a blank block.
2. Two Config SourcesBaked-in bk-config script tag (priority 1), then URLSearchParams (priority 2). Only declared parameters survive; unknown keys dropped by buildConfig().
3. Theme & Accent on Every Widgettheme=auto|light|dark sets data-theme on <html> and follows prefers-color-scheme when auto; accent writes --accent, with derived shades via color-mix(in oklab, …).
4. Namespaced StateWidgets that save browser state use notion-arena.<slug>.v1 and wrap storage access in try/catch. State stays in one browser, never syncs — shared trackers belong in native recipes.

Plus: body { overflow: hidden } with .wrap managing its own scroll (one scrollbar, not two), a prefers-reduced-motion escape hatch, and clipboard exports that always also console.log the payload as a fallback.


🏃 Running It Locally

bash
# Install dependenciesnpm install
# Restore 13 design/dev skills into .agents/skills/npx skills experimental_install -y
# Start dev servernpm run dev          # http://localhost:3000

Requirements: Node 22+, Next.js 16 (Turbopack), React 19, Tailwind v4, TypeScript.

bash
# Type-checknpx tsc --noEmit
# Widget contract checks (offline HTML validation)npm run check:widgets
# Contrast auditnpm run audit:contrast
# Production buildnpm run build
# MCP servernpm run generate:mcp-catalog  # 143 components → mcp/src/data/catalog.jsonnpm run build:mcp             # build notion-arena-mcpnpm run dev:mcp               # run MCP server with tsx (stdio)

Set NEXT_PUBLIC_SITE_URL in production to https://notionarena.vercel.app so registry manifests emit absolute URLs for the right host. Without it, URLs are derived from the request's forwarded host, falling back to https://notionarena.vercel.app (or http://localhost:3000 in local dev).


📁 Project Layout

public/widgets/*.html      the products: 192 self-contained HTML fileslib/catalog.ts             source of truth for all 203 componentslib/types.ts               component/param types + the 8 categorieslib/widget.ts              config coercion, injection, HTML rendering  (server)lib/widget-url.ts          URL builders                                (browser-safe)lib/notion/schema.ts       Notion API payload builderslib/notion/installer.ts    executes plans against @notionhq/clientlib/recipes/               11 recipe declarations + planInstall()lib/registry.ts            shadcn-compatible manifest generationcomponents/                site UI, catalog browser, configurator, docs proseapp/embed/[slug]/          framed, configured widget HTMLapp/api/widget/[slug]/     the same HTML as a downloadapp/r/[name]/              registry: index.json, schema.json, {name}.jsonapp/api/install/           plan | embed | html-block | apidocs/RESEARCH.md           the research behind all of itskills/notion-arena/       AI agent skill (workflow, channels, contract)mcp/                       MCP server (tools for agents)

📦 The Registry (shadcn-compatible)

bash
GET /r/index.json          the whole catalogGET /r/{name}.json         one item, HTML or recipe JSON inlineGET /r/schema.json         JSON Schema of every widget's parameters
jsonc
// mcp config / components.json{ "registries": { "@notion-arena": "https://notionarena.vercel.app/r/{name}.json" } }
bash
# see exactly what an install will do: no credentials, touches nothingcurl -X POST localhost:3000/api/install \  -H 'content-type: application/json' \  -d '{"component":"crm-pipeline","mode":"plan"}'
# then run itcurl -X POST localhost:3000/api/install \  -H 'content-type: application/json' \  -d '{"component":"crm-pipeline","mode":"api",       "token":"'"$NOTION_TOKEN"'","parentPageId":"'"$PAGE_ID"'"}'

mode: "plan" requiring no token is deliberate: review the request sequence before authorising any write to your workspace.


⚠️ Two Things Worth Knowing

A widget cannot read or write your Notion data. Notion's HTML block sandbox has no network access and no bridge to its parent page. Widgets may keep user-entered personal state in this browser, but that state is not Notion data and is not shared. If a workflow needs workspace records, collaboration, permissions, or an audit trail, use a native database or recipe.

Relations force a two-pass install. Since Notion split databases from data sources, a relation property targets a data_source_id that does not exist until the target database has been created and read back. planInstall() therefore emits: create databases with base properties → read back each data source id → patch in relations → patch in rollups → patch in formulas → views → seed rows → pages → block bodies in chunks of 100.

Recipes also declare what they cannot do. Four real API gaps (no button block type, no automation endpoint, no recurring-template endpoint, no synced-block duplicates) appear as manual[] steps, each citing the limitation. A manual step whose reason is "it's easier by hand" is rejected.


🤝 Contributing

We welcome contributions! Whether it's a new widget, a native recipe, a bug fix, documentation, or an idea — here's how to contribute.

[Contribution Flow]

Quick Start for Contributors

  1. Open an Issue — Discuss your idea first. Check for duplicates. Get maintainer feedback.
  2. Fork & Clone — Create your branch: git checkout -b feat/my-widget
  3. Develop — Follow the widget contract (see checklist below)
  4. Test — Run all checks locally
  5. Pull Request — Clear title, link issue, screenshots/GIFs, update CHANGELOG
  6. Review — Maintainer review, CI checks, widget contract audit
  7. Merge — Auto-deploy to Vercel, MCP catalog regenerates, available immediately

Widget Authoring Checklist

Every widget must pass all checks before merge — see scripts/check-widgets.mjs.

[Widget Checklist]

Adding a New Widget

  1. Create public/widgets/my-widget.html (single HTML file, self-contained)
  2. Add entry to lib/catalog.ts with all required fields:
    typescript
    {  slug: "my-widget",  name: "My Widget",  emoji: "🎯",  tagline: "One-line hook",  description: "Full paragraph explaining what it does and why.",  category: "time", // time | dashboards | trackers | planning | business | docs | visuals | automations  kind: "widget",  tier: "free", // free | pro  tags: ["tag1", "tag2"],  color: "blue", // red | orange | yellow | green | blue | purple | pink | brown | gray  params: [    { key: "param1", label: "Label", type: "number", default: 10, min: 1, max: 100 },    { key: "theme", label: "Theme", type: "select", default: "auto", options: [...] },    { key: "accent", label: "Accent", type: "color", default: "#2383e2" },  ],  features: ["Feature 1", "Feature 2"],  useCases: ["Use case 1", "Use case 2"],  capabilities: {    interactive: true,    offlineSafe: true,    persistsLocally: false,    writesToNotion: false,    needsNetwork: false,  },}
  3. Run npm run check:widgets and npm run typecheck
  4. Test in Notion (embed + HTML block)
  5. Submit PR

Adding a Native Recipe

  1. Create recipe in lib/recipes/my-recipe.ts exporting planInstall() and schema
  2. Add entry to lib/catalog.ts with kind: "native" and recipe: "my-recipe"
  3. Run npm run generate:mcp-catalog and npm run build:mcp
  4. Test with mode: "plan" then mode: "api"
  5. Submit PR

Code Style

  • TypeScript strict mode — no any, explicit types
  • Tailwind v4 — utility-first, no custom CSS unless necessary
  • React 19 — server components by default, 'use client' only when needed
  • Conventional Commits — feat:, fix:, docs:, chore:, refactor:

📜 Honesty Policy

  • No fabricated install counts, star counts, or customer logos
  • Badges are qualitative (new, popular, staff-pick) and derived from the catalog
  • Market numbers appear only where cited
  • Capability claims are booleans in the catalog (interactive, offlineSafe, persistsLocally, writesToNotion, needsNetwork) exposed in the registry so an agent can filter on them instead of reading prose

📄 License

MIT License — see LICENSE for details.

Components you download are yours: modify them, host them, ship them in templates you sell. Free components carry no attribution requirement. See /legal/terms.


🔗 Links


Made with ❤️ by SynergyFlow Labs and contributors

[GitHub Stars] [GitHub Forks] [GitHub Issues] [GitHub PRs]

Source: README.md at commit e09613e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestOct 12, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Notion integrations