Skip to content

MCP servers › dev.nucleowp › nucleo

MCP server · registry snapshot 2026-11-14 · last checked 2026-11-14

nucleo MCP server

Registry name dev.nucleowp/nucleo

Nucleo for WordPress — the publisher's title

by nucleowp.dev · domain (the registry's namespace rule)repository owner on GitHub: nucleowp (organization)Source ↗Website ↗

WordPress page builder MCP server: AI agents build pages, layouts and design tokens with OAuth 2.1. — the publisher's description

4 of 5 record checks metversion 0.5.2PHPstreamable HTTP

Summary

dev.nucleowp/nucleo is a remote MCP server listed in the official MCP registry at version 0.5.2, under the namespace of the domain nucleowp.dev. Its linked repository is github.com/nucleowp/nucleo; GitHub reports its owner as nucleowp, an organization.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Repository
public
Last tested
not tested

Tool list

Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.5.2, published 2026-11-14 (registry, as of the 2026-11-14 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-09 to 2026-11-14; 3 in the 90 days before the 2026-11-14 snapshot.
Most recent 3 versions
  • 0.5.2 · 2026-11-14
  • 0.5.1 · 2026-11-14
  • 0.4.1 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-14
Package and repository
checked 2026-11-14

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.4.1 (published 2026-11-09) → 0.5.2 (published 2026-11-14), between the registry lists of 2026-11-13 and 2026-11-14.

The publisher’s GitHub release note for v0.5.2 (“Nucleo 0.5.2”), published 2026-11-14.

Read the release note (the publisher’s text, shown as plain text)
## Changes

- Action needed: saved form submissions use the meta keys `_nucleo_form`, `_nucleo_data` and `_nucleo_context` instead of `_nc_form`, `_nc_data` and `_nc_context`. The update renames the existing ones.
- Improved: the Friendly Captcha widget is updated to 1.1.5.
- Improved: JSON-LD is printed with `wp_get_inline_script_tag`.
- Improved: the readme says that layouts are printed by the Nucleo Canvas theme.
- Fixed: three PHP files were missing the `ABSPATH` check.
- Fixed: the package for WordPress.org no longer shows settings and integrations whose code it does not contain.

## Install

1. Download `nucleo-canvas-0.5.2.zip` and `nucleo-0.5.2.zip` below.
2. In WordPress, install the theme first: **Appearance → Themes → Add New → Upload Theme**.
3. Then install the plugin: **Plugins → Add New → Upload Plugin**, and activate Nucleo.
4. To connect Claude, Cursor or another MCP client, follow [Connect an AI agent](https://nucleowp.dev/en/docs/connect-agent/).

The CLI is optional. Requires WordPress 6.9+ and PHP 8.2+.

## Files

| File | Content |
|---|---|
| `nucleo-0.5.2.zip` | The Nucleo plugin, with the MCP server |
| `nucleo-canvas-0.5.2.zip` | Nucleo Canvas, the companion theme |
| `nucleo-cli-0.5.2.tgz` | The local CLI for developers |

The files are the same as on [nucleowp.dev/en/download](https://nucleowp.dev/en/download/). SHA-256:

```text
ec00fa91747a5ba5014598b2c6987783b25bebbc34b0a06e211745c902dec8a7  nucleo-0.5.2.zip
e8533ed409c0358ef684ca3c76030b2f5b9ea6a019726770a609358af17be435  nucleo-canvas-0.5.2.zip
e4ef10b0e6f846c6c78cd9689755f15c5bfbdf3bfd36e5852d04c184ce559b4d  nucleo-cli-0.5.2.tgz
```

Documentation: [nucleowp.dev/en/docs](https://nucleowp.dev/en/docs/) · Changelog: [nucleowp.dev/en/changelog](https://nucleowp.dev/en/changelog/)

The release on GitHub

Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14; release notes from the GitHub Releases API, checked 2026-11-14.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://{site_host}/wp-json/nucleo/v1/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "nucleo": {
      "url": "https://{site_host}/wp-json/nucleo/v1/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "nucleo": {
      "type": "http",
      "url": "https://{site_host}/wp-json/nucleo/v1/mcp"
    }
  }
}
Claude Code
claude mcp add --transport http nucleo "https://{site_host}/wp-json/nucleo/v1/mcp"
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "nucleo": {
      "type": "streamableHttp",
      "url": "https://{site_host}/wp-json/nucleo/v1/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "nucleo": {
      "httpUrl": "https://{site_host}/wp-json/nucleo/v1/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nucleo]
url = "https://{site_host}/wp-json/nucleo/v1/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "nucleo": {
      "url": "https://{site_host}/wp-json/nucleo/v1/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{site_host}/wp-json/nucleo/v1/mcp" --transport http
  • The URL contains parts in { } that the entry marks as variables; replace them with your own values.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/nucleowp/nucleoOpens publiclymatchesapi.github.com · 2026-11-14

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
dev.nucleowp
GitHub owner
an organization (nucleowp)
Repository
github.com/nucleowp/nucleo
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about dev.nucleowp/nucleo

Answered from the data above

Who publishes dev.nucleowp/nucleo?

The registry ties the namespace dev.nucleowp to the domain nucleowp.dev; only its owner can publish under it. Its linked repository is github.com/nucleowp/nucleo; GitHub reports its owner as nucleowp, an organization. These are facts from the registry and GitHub, not a rating.

Is dev.nucleowp/nucleo safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has dev.nucleowp/nucleo been security tested?

No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

Does dev.nucleowp/nucleo publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of dev.nucleowp/nucleo?

In github.com/nucleowp/nucleo, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-14; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-14
Hosting type
registry · 2026-11-14
MCP capability
not checked
not read (no session)
Transport
streamable HTTP
registry · 2026-11-14
Required credentials
none declared
registry · 2026-11-14 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-14
Lifecycle status
registry · 2026-11-14
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-14
Maintenance
api.github.com · 2026-11-14
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-14

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.nucleowp/nucleo: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/dev.nucleowp/nucleo

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.nucleowp/nucleo)](https://protocolprobe.com/mcp/servers/dev.nucleowp/nucleo)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology