If you’re building developer tools in 2026, forcing users to type prompts exclusively inside a web UI feels increasingly outdated. IDE extensions, terminal agents like Claude Code, and desktop AI clients are where developers spend their time.
We just shipped an architectural upgrade to NextBlock CMS: Cortex AI is now a native MCP Server.
How the Architecture Works
NextBlock exposes a route handler at /api/mcp using Streamable HTTP/SSE protocol transport, fully aligned with the MCP specification.
[VS Code / Cursor / Claude / ChatGPT]
│
│ (Streamable HTTP/SSE / Bearer Auth)
▼
┌──────────────────────────────────────────────┐
│ NextBlock /api/mcp Route Handler │
├──────────────────────────────────────────────┤
│ Cortex AI Tool Registry │
│ - get_database_schema │
│ - generate_jsonb_layout │
│ - query_site_analytics │
│ - update_navigation │
└──────────────────────┬───────────────────────┘
│
▼
┌──────────────────────────────────────────────┐
│ Supabase / PostgreSQL (JSONB) │
└──────────────────────────────────────────────┘
Local & Remote Flexibility
Local Development: When hacking on http://localhost:3000, you can point your local .claude/settings.json directly to /api/mcp. Your local AI agent can query your Supabase instance, draft new page components, or seed test data without touching the browser.
Production & BYOK: In-browser users still enjoy zero token markup via BYOK OpenRouter keys, while production sites can expose secure MCP endpoints protected by token authentication.
Because NextBlock stores content as strict PostgreSQL JSONB rather than legacy raw HTML strings, LLM tool calls generate typed, schema-valid UI nodes that insert cleanly into React Server Components (RSC) with zero sanitization tax.
Jump into the repo, try adding the MCP server to your local Claude setup, and let us know what tools you want us to expose next!
🐙 GitHub: https://github.com/nextblock-cms/nextblock
⚡️ Live Demo: https://nextblock.dev
Top comments (0)