Developer · Remote MCP server
NextBlock CMS
Manage pages, posts, blocks, media and settings of your self-hosted NextBlock site.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.nextblock/nextblock- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-18
- Updated
- 2026-09-18
- Publisher
- dev.nextblock
- Namespace
- Namespace verified by the MCP Registry via the domain nextblock.dev · how
- Website
- nextblock.dev
- Repository
- github.com/nextblock-cms/nextblock
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{site_host}/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect NextBlock CMS
NextBlock CMS is a remote MCP server: there is nothing to install. Its endpoint is https://{site_host}/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {site_host}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| New Relic MCP ServerMonitor, troubleshoot, and optimize your technology stack with Observability. | Remote · HTTPLive check: sign-in required |
| Newton BrowserLocal-only Chrome and Edge control for MCP clients through an origin-scoped extension. | Local · stdio |
| NexQL Postgres MCPStandalone Postgres MCP server - schema-aware, read-only by default, installable everywhere. | Local · stdio |
| NexsusPrivate persistent memory for Claude, ChatGPT & Gemini via MCP - semantic search, zero-code setup. | Remote · HTTPLive check: sign-in required |
| NexusZero-setup MCP gateway securely connecting AI to your tools with authentication and workflows. | Remote · HTTPLive check: sign-in required |
| NexusQuery Sonatype Nexus Repository (OSS/Pro) for Maven, Python, and Docker artifacts. | Local · stdio |
| NEXUS AIDeploy full-stack apps with databases, storage, backups, logs, scaling, and rollback. 74 MCP tools. | Remote · HTTPLive check: sign-in required |
| Nexus Browser MCPEvent-driven deterministic browser MCP: HITL gates, audit, console/network/perf observability. | Local · stdio |