MCP.so
Sign In

NextBlock CMS MCP ServerVerifiedFeatured

@NextBlock

Basic information

Transport

Streamable HTTP

Authentication

API Key

Category

Developer Tools

Author

NextBlock

Submitted by

NextBlock

About NextBlock CMS MCP Server

Open-source Next.js + Supabase CMS with a per-site MCP server: scaffold a site, then create pages, posts, navigation, media and SEO from Claude, Cursor or any MCP client. Streamable HTTP with a bearer token you mint in your own CMS.

Connection details

https://cms.nextblock.dev/api/mcp

Setup

claude mcp add nextblock --transport http https://cms.nextblock.dev/api/mcp --header "Authorization: Bearer <token from Settings > Cortex AI > MCP server access>"

NextBlock CMS MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is NextBlock CMS

NextBlock is a free, open-source (AGPL) CMS and website builder for Next.js 16, Supabase and Tailwind CSS: a Notion-style block editor, Live Draft Mode, a built-in SEO engine, bilingual content, media library, forms and e-commerce. Every NextBlock site ships its own MCP server at https://<your-site>/api/mcp, so a coding agent can build and edit the whole site. The endpoint listed here is the public demo instance.

What the MCP server can do

56 tools, 3 resources and 4 prompts, including:

  • get_site_overview, create_page_layout, generate_jsonb_layout, insert_content_block, update_content_block
  • update_site_navigation, update_navigation_bar, update_footer, update_site_identity, manage_site_theme
  • create_cms_post, create_cms_product, translate_page, translate_content_bulk
  • upload_media, search_stock_photos, set_content_images
  • publish_content_draft: generated layouts stage as Live Drafts; nothing goes live until you publish

Prompts: build-site (interview → plan → build), build-page, clone-from-url, translate-content.

Connect in three steps

  1. Scaffold a site: npx create-nextblock@latest my-site --non-interactive (Node 20+, Docker Desktop for the local profile; add --mode cloud to use a Supabase project instead). Or deploy to Vercel in one click from the repository README.
  2. In the CMS open Settings → Cortex AI → MCP server access, enable the server and mint a token (read-only or read+write; revoke any time). The MCP server is part of Cortex AI, which has a free 30-day trial with no credit card.
  3. Add the server to your client with the configuration above. Claude Code needs "type": "http"; Cursor infers it; VS Code uses a top-level servers block with an input prompt for the token. The CMS generates the exact snippet for each client.

Authentication

Streamable HTTP with Authorization: Bearer <token>. Tokens are per site and per scope; there is no OAuth flow and no shared credentials. The demo instance requires a token too, so use your own site for anything real.

Links

Frequently asked questions

1

What is the NextBlock CMS remote MCP server?

The NextBlock CMS remote MCP server is a hosted Model Context Protocol endpoint at https://cms.nextblock.dev/api/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the NextBlock CMS MCP server?

Add the endpoint https://cms.nextblock.dev/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the NextBlock CMS MCP server require authentication?

Yes. NextBlock CMS requires an API key — check the official documentation for how to obtain one, then include it in your client's configuration.

4

Which transport does the NextBlock CMS MCP server use?

NextBlock CMS exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments