Back to Articles
Diagram of Cortex AI Model Context Protocol MCP connection to external LLMs
Cortex AISeptember 10, 20267 min read

Connect Claude to NextBlock CMS via MCP, from Cursor or Claude Code

A hands-on guide to the Cortex AI MCP server: what it fixes, which tools it exposes, and the exact config for localhost and production.

This guide shows you how to connect Claude to NextBlock CMS with an open standard instead of a vendor plugin. Cortex AI turns your site into a Model Context Protocol server. Claude Code, Cursor, ChatGPT, and Gemini can then read your database schema, draft page layouts, and update navigation from their own chat window. You pay for the AI subscription you already have, with no token markup in between.

One config block

Setup in minutes.

Paste one JSON entry into Claude Code, Cursor, or VS Code. The CMS settings card writes it for you.

Free to try

30 days, no credit card.

The CMS is free forever. Cortex AI, which includes the MCP server, starts with a 30-day free trial.

Live Drafts

Nothing ships by accident.

Every layout the agent writes lands as a draft. An editor reviews it and hits publish.

Every prompt becomes a structured database record rather than a pile of generated code. Your editors keep a visual CMS, your developers keep a clean Next.js 16 app, and nothing goes live until someone hits publish.

The Problem with Traditional AI Web Builders

Prompt builders such as Lovable, Bolt, and v0 are impressive on day one. You describe a page and get a working React app in minutes. The trouble starts on day two.

Side by side

Prototype tools versus NextBlock.

What happens after the first prompt.

What you getLovable, Bolt, v0NextBlock
Day oneDisposable code with no content layer.A live Next.js 16 and Supabase website with a CMS.
Changing a headlineAnother prompt or another pull request.An editor types it in a Notion-style editor.
Drafts and revisionsCode history only.Live Drafts, revisions, and one-click restore.
Translations and SEONot built in.Per-block translation and SEO checks as you type.
AI costsPlatform credits, bought from the tool.Your own subscription over MCP, no markup.
PriceA monthly plan.Free CMS. Cortex AI after a 30-day free trial.

NextBlock takes the opposite view from the prototype tools. AI should draft the site, and people should own it. The MCP connection is how those two worlds meet.

How Cortex AI Uses Model Context Protocol (MCP)

Model Context Protocol is an open standard for giving AI agents tools. A client such as Claude Code lists the tools a server offers, calls them with typed arguments, and reads typed results back. Cortex AI ships that server inside your NextBlock install at /api/mcp.

Model Context Protocol · NextBlock Cortex AI

From prompt to production, without a redeploy.

Your AI client talks to the CMS over an open standard. Output lands as data, not as code you have to host.

Step 1 · Your AI client

Prompt

Any MCP client you already pay for.

Claude CodeCursorChatGPTGemini

One JSON block in your client config registers the server. That is the setup.

Your subscription · no token markup

Step 2 · /api/mcp

Cortex AI MCP server

Streamable HTTP · bearer token · scoped.

get_database_schemagenerate_jsonb_layoutupdate_site_navigationquery_site_analyticssearch_stock_media

5 contract tools · 29 typed tools

Step 3 · PostgreSQL

Validated JSONB blocks

Supabase · one Zod schema per block.

Staged as a Live Draft.

Editors refine in the visual CMS.

Revisions and SEO checks built in.

Nothing goes live until publish

Step 4 · Next.js 16

Published page

Server Components · edge cached.

No rebuild, no redeploy.

100/100 Lighthouse defaults.

Same site on day two.

A website plus a CMS

Editors keep a visual CMS. Developers keep a clean Next.js 16 codebase. The agent never touches either.

The endpoint speaks Streamable HTTP. Your client posts JSON-RPC messages over a normal HTTPS request, and the server answers in the same response. There is no long-lived SSE stream to babysit and no SDK to install on the server side. The same 29 typed tools that power Cortex AI inside the editor are exposed over the wire, so the agent in your IDE and the agent in your CMS never drift apart.

Safety rule one

Layouts stage as Live Drafts.

Layout tools write drafts, so nothing reaches visitors until an editor publishes it.

Safety rule two

Every token carries a scope.

A read-only token never even sees a tool that could change data. Mutating tools are absent from its list.

Available MCP Database Tools

Five tool names form the public MCP contract. Each one forwards to a tested Cortex AI executor.

get_database_schemaread

Returns every table the agent may read or change, with columns, primary keys, and read-only flags.

generate_jsonb_layoutwrite

Turns a prompt into a full page layout, validates each block against the NextBlock schema, and stages it as a Live Draft.

update_site_navigationwrite

Adds, renames, or reorders header menu items per locale.

query_site_analyticsread

Reads revenue, order counts, status breakdowns, and top products over a date range.

search_stock_mediaread

Finds free stock photos with alt text and photographer credits ready for an image block.

And 24 more.

Create posts and products, translate pages, upload media, manage themes and scripts. Three resources expose the database, block, and custom block schemas.

Step by Step: Connect Claude to NextBlock CMS in Cursor and Claude Code

The server is off by default because it is a remote write surface onto live content. Turning it on takes three steps, and the trial means the first month costs nothing.

01

Start the free trial.

Open CMS Settings → Cortex AI, start the 30-day trial with no credit card, and switch on the MCP server access card.

02

Mint a token.

Pick the scope you need. Read-only is enough for planning and audits.

03

Copy the config.

The card renders one snippet each for Claude Code, Cursor, VS Code, and Claude Desktop.

Claude Code needs "type": "http" in the entry, or it skips the server without a warning. Cursor infers the transport from the URL and needs no type field. VS Code uses a top-level servers key and prompts for the token instead of storing it.

Localhost Configuration Without a Token

While you build, turn on Trust localhost without a token in the same settings card. A dev server on your machine then accepts loopback calls with no header at all. Standalone installs run on port 3000, and the monorepo dev server runs on port 4200.

Add this block to .mcp.json in your project root for Claude Code.

.mcp.json
{
  "mcpServers": {
    "nextblock": {
      "type": "http",
      "url": "http://localhost:3000/api/mcp"
    }
  }
}

The CLI form does the same thing in one line.

terminal
claude mcp add --transport http nextblock http://localhost:3000/api/mcp

Development only

Localhost trust is ignored in production builds, because a proxy can spoof the host header. Production always uses a token.

Production Authentication via Bearer Tokens

In production every client sends a bearer token. Tokens start with nbmcp_, are shown once at mint time, and are stored only as SHA-256 hashes. Revoking one is a single click, and the same value can never be minted again.

Add this to .cursor/mcp.json for Cursor, or drop the same entry into .mcp.json with a type field for Claude Code.

.cursor/mcp.json
{
  "mcpServers": {
    "nextblock": {
      "url": "https://your-site.com/api/mcp",
      "headers": { "Authorization": "Bearer nbmcp_your_token" }
    }
  }
}

Try it

Once the client connects, ask for something concrete. Try “inspect the database schema and draft a pricing page with three tiers.” The agent calls the schema tool, then the layout tool, and your CMS shows a new Live Draft ready for review.

Zero-Redeploy Production Rendering

The reason this works is where the output lands. Cortex AI writes strict JSONB block records into PostgreSQL, not HTML strings and not source files. Each block has a Zod schema, so a bad field is rejected before it is stored.

0

Rebuilds to publish

1

Zod schema per block

100

Lighthouse by default

At request time Next.js 16 renders those records with Server Components and caches the result at the edge. There is no build step between publish and live, and no HTML sanitizer tax on every render. The 100/100 Lighthouse defaults you get on an empty site are the same ones you get after the agent has drafted fifty pages.

Next step

Up in ten minutes, free for thirty days.

Deploy the free CMS to Vercel in one click, start the Cortex AI trial with no credit card, and connect Claude to NextBlock CMS today. Read how the block registry keeps all of it safe if you want the full picture.

Discussion & Comments

Join the conversation and express your thoughts.

Please log in to write a comment.