nextblock-cms

MCP开发工具

提供方 NextBlock

开发工具 Streamable HTTP OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeCodex

由 NextBlock 提供的 MCP 服务器,Streamable HTTP。

一句话选型结论

按资料字段整理

nextblock-cms 属于开发工具类 MCP 服务器,Streamable HTTP,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式Streamable HTTP 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

cms nextjs supabase website builder headless cms seo remote

支持客户端

适用场景

cmsnextjssupabase

安装与配置

Streamable HTTP OAuth 授权
新一代远程传输,替代 SSE
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
nextblock-cms当前 未标注 Streamable HTTP 远程部署 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方NextBlock上游标注的维护方 NextBlock
分类开发工具本站按上游分类展示
连接方式Streamable HTTP新一代远程传输,替代 SSE
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

15.9 KB
来自项目仓库与上游目录的原文,未做删改

NextBlock™ CMS

The open-source, full-stack AI-native CMS for Next.js 16, Supabase, and Tailwind CSS.

Deploy a production Next.js 16 + Supabase website and CMS in one click.

Vercel provisions the database and injects its keys before the first build, NextBlock applies its own

schema during that build, and the in-app wizard asks only for your admin account.

No environment variables to fill in.

Live Sandbox
Documentation
Deploy Guide
GitHub

Sandbox resets every 15 minutes · User: demo@nextblock.dev · Pass: password


🚀 Why NextBlock™?

Tired of slow WordPress sites? Finding headless CMSs too complex? NextBlock™ is the sweet spot.

We combined the flexibility of a Block Editor with the raw power of Next.js 16 Server Components. The result is a CMS that feels like a static site but manages like a dynamic platform.

✨ Key Features

  • ▲ Next.js 16 App Router + React 19 Server Components: the public site renders on the server — page, article and product routes are all Server Components — with client components reserved for cart, checkout, forms and the CMS dashboard.
  • 🗄️ Supabase PostgreSQL with JSONB block storage: every content block is a row in public.blocks with a jsonb content column. User-defined block types live in custom_block_definitions (fields / layout_schema as jsonb, guarded by Postgres CHECK constraints) and render without a rebuild.
  • 🚀 Zero-config 1-click migrations: the Vercel Supabase integration provisions the database and injects its keys before the first build; NextBlock then applies its own forward-only migrations during that build (tools/build-migrate.mjs), with a runtime fallback in the /setup wizard. Nothing to run, nothing to paste.
  • ⚡ 100/100 Lighthouse: Perfect scores across Performance, Accessibility, Best Practices and SEO — 0.3 s FCP, 0.8 s LCP, 0 ms Total Blocking Time and 0 Cumulative Layout Shift on a production build. AVIF/WebP images with a one-year cache TTL, critical-CSS inlining and tree-shaken imports are the defaults, not plugins.
  • 🤖 Built for AI Agents: Our codebase is documented and structured specifically to be easily read and extended by AI coding assistants.
  • 🛍️ E-Commerce Ready: Premium commerce package for digital products, checkout providers, currency, tax, and shipping management.
  • 🧱 Visual Block Editor: A reusable Tiptap-powered Notion-style editor that your clients will actually enjoy using.
  • 🔓 Open-Core Model: The core is 100% Free & Open Source (AGPL). Premium modules (today Cortex AI and Commerce Pro, with more to come) ship in every install and switch on in the CMS with a free 30-day trial (no credit card) or a license key.

🆚 The NextBlock™ Advantage

Feature NextBlock™ CMS WordPress Payload / Strapi
Tech Stack Next.js 16 + Supabase PHP + MySQL React / Node.js
Architecture Nx Monorepo Monolith Monolith / Workspaces
Performance 🟢 100/100 (Default) 🔴 Bloated (Plugins) 🟡 Spec-dependent
Security 🔒 Static/Edge First 🔓 Plugin vulnerabilities 🔒 Secure
DX 💎 React Server Components 📜 Legacy PHP Hooks 🧩 Config Heavy
AI Ready ✅ Native ❌ No 🟡 Integration required

🏁 Get Started

☁️ Option 1 — Deploy to the cloud in one click (recommended)

During import, Vercel's native Supabase Marketplace integration (the stores
button parameter) prompts you to create a Supabase database (name + region), then
provisions it, connects it to the project, and injects its keys before the first
build
— you never copy a value, and there are no environment variables to fill in
(the site URL defaults to your *.vercel.app URL and the app secrets are derived
automatically). The app boots with the database already connected: the wizard
auto-skips the connection step, applies the schema for you, uses the connected Supabase
project for media storage, and leaves just "create your admin." Full walkthrough:
docs/12-VERCEL-DEPLOYMENT.md.

> Tip — keep the new repo public. When Vercel asks, leave "Create private Git
> Repository" unchecked
. On the free (Hobby) plan, automatic upstream updates only deploy
> from a public repo — Hobby blocks bot-authored deploys on private repos — and public
> also makes update checks fully tokenless. You can change visibility later in the repo's
> GitHub settings if you change your mind. Details: docs/13.

💻 Option 2 — Scaffold locally with the CLI

Stop cloning heavy repos. Start with our CLI and get a production-ready app instantly.```bash
npm create nextblock@latest


This runs the `create-nextblock` CLI, which scaffolds the canonical application. The CLI no longer asks for credentials in the terminal — once the project is created, start it and finish setup in your browser:```bash
cd <your-project>
npm run dev   # then open http://localhost:3000/setup

The First-Boot Setup Wizard at /setup walks you through connecting Supabase, configuring storage / email, and creating the first administrator. Every fresh instance redirects there automatically until an admin exists.

> Want a fully local, zero-config sandbox? Use Local Self-Hosted Docker Mode — one command spins up the entire stack (Supabase engines + S3 storage + the app) on your own machine, with no cloud accounts. The app boots straight into the /setup wizard with MinIO storage pre-filled. See docs/11-SELF-HOSTED-DOCKER.md.

🤖 Option 3 — Let your coding agent build it

NextBlock ships as an MCP server (https:///api/mcp, Streamable HTTP, bearer token) and as an agent plugin, so Claude Code, Cursor, Codex and friends can scaffold a site and then build every page over MCP.

  • Claude Code — this repo is its own plugin marketplace:text /plugin marketplace add nextblock-cms/nextblock /plugin install nextblock@nextblock

Then ask for a website, blog or store; the nextblock skill proposes NextBlock, runs npx create-nextblock@latest my-site --non-interactive, and hands you the two browser steps (create your admin, start the free Cortex AI trial). Source: plugins/nextblock.
- Cursor — the same folder is a Cursor plugin (.cursor-plugin/plugin.json, rule + skill + MCP server): install it from this repo via Customize → Plugins → From GitHub Repository, or copy plugins/nextblock/rules/nextblock.mdc into your project's .cursor/rules/.
- Codex, Jules and other agents — paste the block from plugins/AGENTS.snippet.md into your AGENTS.md. Codex also loads the folder as an Agent Plugin (plugins/nextblock/plugin.json) through this repo's marketplace manifest.
- Any MCP client — the official MCP Registry entry dev.nextblock/nextblock (server.json) prompts for your site host and token; the public demo instance is https://cms.nextblock.dev/api/mcp. Every NextBlock site also serves /llms.txt and, where the MCP server is enabled, /.well-known/mcp/server-card.json.


🏗️ For Contributors: The Factory

> Note: You are currently looking at the Nx Monorepo (The Factory), not the generated product template.
>
> NextBlock™ is an Nx monorepo for a Next.js 16 CMS backed by Supabase. The repo contains the canonical application, the create-nextblock CLI, shared editor and UI packages, the database and migration layer, and the premium ecommerce module.

🧩 Main Surfaces

  • apps/nextblock: canonical public site and CMS application
  • apps/create-nextblock: scaffolding CLI and template sync pipeline
  • libs/db: Supabase clients, package activation checks, migrations, and db types
  • libs/editor: reusable Tiptap editor package
  • libs/ecommerce: premium commerce package and CMS commerce screens
  • libs/sdk: typed block extensibility contract
  • libs/ui, libs/utils: shared primitives and helpers

⚡ Developer Quickstart

Prerequisites — configuration happens in the browser, but the /setup wizard asks for these, so create them first:

  1. Supabase project (dashboard) — you'll need the Reference ID (Project Settings → General), the connection string (Connect → Direct connection → URI), the anon + service_role keys (Project Settings → API Keys), and a Personal Access Token (Account → Access Tokens → Generate new token).
  2. Cloudflare R2 bucket (optional — without one, media goes to the Supabase project's own Storage) (dashboard → R2) — create a bucket, enable its Public Development URL (Bucket → Settings → General), then create an Account API token (R2 → Manage API Tokens) with Object Read & Write. Copy the Access Key ID and Secret Access Key — the secret is shown only once.
  3. SMTP credentials (optional, configurable later in the CMS; SMTP2GO works very well) — needed for password resets and invitations. The first administrator is confirmed instantly and needs no email.

Then run:```bash
git clone https://github.com/nextblock-cms/nextblock.git
cd nextblock
npm install
npm run setup
npm run dev


`npm run setup` is informational only — it prompts for nothing and writes no files. `npm run dev` is the root alias for `npx nx serve nextblock`. Open **http://localhost:4200/setup** and the browser wizard connects Supabase, applies the schema, configures storage, and creates your first administrator.

**First login:** the dev server runs at **http://localhost:4200**. The wizard creates your administrator (confirmed instantly, no email needed) and signs you in. You land on the Cortex AI welcome offer, one click away from the CMS at `/cms/dashboard`.

#### 🐳 Or: one-click local stack (no cloud accounts)

Prefer to run everything on your machine? With **Docker Desktop** running:```bash
git clone https://github.com/nextblock-cms/nextblock.git
cd nextblock
npm install
npm run docker:setup     # or: npm run setup → pick "Local Self-Hosted Docker Mode"

This builds and boots the full self-hosted stack (Postgres + GoTrue + PostgREST + Kong, MinIO for media, and the app) and applies migrations automatically — the only prompts are optional Turnstile and SMTP. The app runs at http://localhost:3000 and the first sign-up becomes ADMIN (auto-confirmed, no email step). Manage it with npm run docker:up / docker:down / docker:logs. Full guide: docs/11-SELF-HOSTED-DOCKER.md.

🔄 Keeping an install up to date

Whichever way NextBlock was installed, one command brings the code, the dependencies and the
database schema forward together:bash npm run update # code + dependencies + schema npm run update -- --check # report what would change; write nothing

  • One-click Vercel / GitHub fork / clone — already automatic: a daily GitHub Action
    merges upstream and Vercel redeploys. Run the command when you want it now.
  • npm create nextblock projects — new framework code comes from the published
    create-nextblock package and is applied as a git 3-way merge, so your edits to
    framework files survive and only genuine overlaps conflict. Docker installs follow it with
    npm run docker:up.

The automatic Action depends on your repository being this monorepo — not on where the site
is hosted. See docs/13 for the full picture.

🛠️ Useful Commands

  • npm run update - Update code, dependencies and database schema (any install type)
  • npm run update -- --check - Preview an update without changing anything
  • npm run dev - Start the local development server for the CMS on http://localhost:4200 (runs npx nx serve nextblock)
  • npm run lint - Lint the monorepo
  • npm run db:types - Generate Supabase types
  • npm run db:migrate:check - Preview pending Supabase migrations safely
  • npm run db:migrate / npm run db:push - Apply pending migration files only, without resets or sandbox seeding
  • npm run db:migrate:repair-history:check - Preview baseline migration-history repair for existing live databases
  • npm run generate:sandbox - Generate sandbox data
  • npm run sandbox:reset - Reset the sandbox environment

📚 Documentation Index

The root docs/ folder is the maintained reference set for both contributors and AI agents.

The template docs are copied from the root docs through the sync pipeline, so this root docs set is the place to maintain first.

Document Purpose
docs/01-PROJECT-OVERVIEW.md Monorepo structure, runtime model, and where each subsystem lives
docs/02-ECOMMERCE-CAPABILITIES.md Verified commerce features, checkout providers, currency, tax, shipping, and fulfillment
docs/03-CMS-AND-EDITOR.md Tiptap editor, page builder, widgets, and built-in block system
docs/04-DATABASE-AND-AUTH.md Supabase clients, auth flow, schema overview, RLS, and migration map
docs/05-DEVELOPER-GUIDE.md Local setup, scripts, db workflow, sandbox reset, and contributor operations
docs/06-CLI-AND-SCAFFOLDING.md create-nextblock, template sync, and generated-project behavior
docs/07-BLOCK-SDK-AND-EXTENSIBILITY.md SDK contract and extensibility model
docs/08-NEXTBLOCK-CORTEX-AI-ARCHITECTURE.md Premium Cortex AI package: model routing, BYOK, inline editor and global agent tools
docs/09-LIVE-DRAFT-MODE.md Real-time visual editing and non-destructive draft previewing
docs/10-CUSTOM-BLOCKS.md Data-driven custom blocks: schema, CRUD, dynamic rendering, and import/export
docs/11-SELF-HOSTED-DOCKER.md One-click local self-hosted Docker stack: Supabase engines, MinIO storage, migration runner, and how it maps to cloud
docs/12-VERCEL-DEPLOYMENT.md One-click cloud deploy, the browser setup wizard, and Supabase env-var aliases
docs/13-STAYING-UP-TO-DATE.md npm run update for all four installs, the daily upstream-sync Action, and how migrations reach a deployed site
docs/README.md Audience-based docs index

> Under the hood note: The migration folder under libs/db/src/supabase/migrations is the best source of truth for current platform capabilities.


🤝 Contributing

NextBlock is open source under AGPL-3.0-or-later, and contributions are welcome.

  • CONTRIBUTING.md — setup, everyday commands, and the repo-specific rules that are easy to trip over (append-only migrations, the generated template, the derived artifacts).
  • CODE_OF_CONDUCT.md — Contributor Covenant v2.1.
  • SECURITY.md — how to report a vulnerability privately. Please never use the public issue tracker for security reports.

🌐 Connect With Us

Join the community and stay updated on the latest features.

  • X (Twitter): @NextBlockCMS
  • LinkedIn: NextBlock™
  • GitHub: nextblock-cms/nextblock
  • Medium: @nextblockcms
  • Dev.to: nextblockcms

🙏 Acknowledgements

Thanks to Vercel for their support of open-source software.


Built with ❤️ by the NextBlock™ Team. Licensed under AGPLv3.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
nextblock-cms 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

nextblock-cms 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是Streamable HTTP,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

nextblock-cms 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

nextblock-cms 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

nextblock-cms 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

nextblock-cms 能提供哪些能力?

资料显示能力标签包括 cms、nextjs、supabase、website builder、headless cms、seo。具体工具清单以官方文档为准。

nextblock-cms 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

nextblock-cms 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为Streamable HTTP。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。