Skip to content
Back to search

nera

MarketplaceWorks with Claude CodeGitHub

A local MCP server for the Nera static site generator. It lets an AI assistant (Claude Code, Claude Desktop, Cursor, Codex or any other MCP client) create, edit, build, validate, preview and publish…

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/seebaermichi/nera-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/seebaermichi/nera-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/seebaermichi--nera-mcp/badge.svg)](/listings/seebaermichi--nera-mcp)

HTML

<a href="/listings/seebaermichi--nera-mcp"><img src="/api/listings/seebaermichi--nera-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Desktop extension

The easiest way, and no Node.js needed: Claude Desktop runs the server on the Node it ships, and the extension brings npm along.

1. Download `nera-mcp-<version>.mcpb` from the [latest release](https://github.com/seebaermichi/nera-mcp/releases/latest). 2. Double-click it and choose **Install** in Claude Desktop. 3. Pick your **Sites folder** when Claude Desktop asks for it: the folder your sites live in.

The extension runs on macOS and Windows. To update, install the `.mcpb` of a newer release.

Claude Code plugin

The plugin brings the server and the Nera skill, which teaches Claude how a Nera site is built, in one install:

claude plugin marketplace add seebaermichi/nera-mcp
claude plugin install nera@nera

or, inside Claude Code 2.1.275 or later, in one step:

/plugin install nera --marketplace seebaermichi/nera-mcp

Claude Code asks for your **Sites folder** when the plugin is enabled. The plugin starts the server with `npx`, so it needs Node.js (see Requirements).

Manual configuration

To add the server to a client yourself, replace `/Users/you/Sites` below with the folder your sites should live in. It must exist. Use an absolute path: clients do not expand `~` in their configuration files.

Claude Code

claude mcp add --transport stdio nera -- npx -y @nera-static/mcp --root /Users/you/Sites

Add `--scope user` to have it in every project, or `--scope project` to share it through the project's `.mcp.json`.

Claude Desktop

Without the extension: Settings → Developer → **Edit Config** opens `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`, Windows: `%APPDATA%\Claude\`). Add the server and restart Claude Desktop:

{
    "mcpServers": {
        "nera": {
            "command": "npx",
            "args": ["-y", "@nera-static/mcp", "--root", "/Users/you/Sites"]
        }
    }
}

Cursor

Add the same `mcpServers` entry to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project).

Codex

codex mcp add nera -- npx -y @nera-static/mcp --root /Users/you/Sites

or in `~/.codex/config.toml`:

[mcp_servers.nera]
command = "npx"
args = ["-y", "@nera-static/mcp", "--root", "/Users/you/Sites"]

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 21 lines
  1. {
  2. "name": "nera",
  3. "owner": {
  4. "name": "Michael Becker"
  5. },
  6. "metadata": {
  7. "description": "Nera, the static site generator, for Claude Code"
  8. },
  9. "plugins": [
  10. {
  11. "name": "nera",
  12. "description": "The Nera skill plus the Nera MCP server: create, edit, build, validate, preview and publish Nera websites inside one sites folder.",
  13. "category": "development",
  14. "homepage": "https://nera.js.org",
  15. "source": {
  16. "source": "npm",
  17. "package": "@nera-static/mcp"
  18. }
  19. }
  20. ]
  21. }
README.md · README · 148 lines
  1. # @nera-static/mcp
  2. [![Test](https://github.com/seebaermichi/nera-mcp/actions/workflows/test.yml/badge.svg)](https://github.com/seebaermichi/nera-mcp/actions/workflows/test.yml)
  3. [![npm version](https://img.shields.io/npm/v/@nera-static/mcp)](https://www.npmjs.com/package/@nera-static/mcp)
  4. A local [MCP](https://modelcontextprotocol.io) server for the [Nera](https://github.com/seebaermichi/nera) static site generator. It lets an AI assistant (Claude Code, Claude Desktop, Cursor, Codex or any other MCP client) create, edit, build, validate, preview and publish Nera sites in one folder on your computer, and nowhere else.
  5. 📖 **Documentation:** [nera.js.org](https://nera.js.org)
  6. ```bash
  7. npx -y @nera-static/mcp --root ~/Sites
  8. ```
  9. The client starts this command itself; you only add it to the client's configuration (below). `--root` is the folder the server may work in: every site it creates lands there, and every path a tool takes is checked against it (no `..`, no absolute path outside it, no symlink leading out).
  10. ## Requirements
  11. - Node.js **22.12 or later** (`node --version`), with `npx`. Not needed for the Claude Desktop extension, which brings its own.
  12. - For `publish`: a GitHub account (and a Netlify account if you host there)
  13. ## Install
  14. ### Claude Desktop extension
  15. The easiest way, and no Node.js needed: Claude Desktop runs the server on the Node it ships, and the extension brings npm along.
  16. 1. Download `nera-mcp-<version>.mcpb` from the [latest release](https://github.com/seebaermichi/nera-mcp/releases/latest).
  17. 2. Double-click it and choose **Install** in Claude Desktop.
  18. 3. Pick your **Sites folder** when Claude Desktop asks for it: the folder your sites live in.
  19. The extension runs on macOS and Windows. To update, install the `.mcpb` of a newer release.
  20. ### Claude Code plugin
  21. The plugin brings the server and the Nera skill, which teaches Claude how a Nera site is built, in one install:
  22. ```bash
  23. claude plugin marketplace add seebaermichi/nera-mcp
  24. claude plugin install nera@nera
  25. ```
  26. or, inside Claude Code 2.1.275 or later, in one step:
  27. ```text
  28. /plugin install nera --marketplace seebaermichi/nera-mcp
  29. ```
  30. Claude Code asks for your **Sites folder** when the plugin is enabled. The plugin starts the server with `npx`, so it needs Node.js (see Requirements).
  31. ### Manual configuration
  32. To add the server to a client yourself, replace `/Users/you/Sites` below with the folder your sites should live in. It must exist. Use an absolute path: clients do not expand `~` in their configuration files.
  33. #### Claude Code
  34. ```bash
  35. claude mcp add --transport stdio nera -- npx -y @nera-static/mcp --root /Users/you/Sites
  36. ```
  37. Add `--scope user` to have it in every project, or `--scope project` to share it through the project's `.mcp.json`.
  38. #### Claude Desktop
  39. Without the extension: Settings → Developer → **Edit Config** opens `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`, Windows: `%APPDATA%\Claude\`). Add the server and restart Claude Desktop:
  40. ```json
  41. {
  42. "mcpServers": {
  43. "nera": {
  44. "command": "npx",
  45. "args": ["-y", "@nera-static/mcp", "--root", "/Users/you/Sites"]
  46. }
  47. }
  48. }
  49. ```
  50. #### Cursor
  51. Add the same `mcpServers` entry to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project).
  52. #### Codex
  53. ```bash
  54. codex mcp add nera -- npx -y @nera-static/mcp --root /Users/you/Sites
  55. ```
  56. or in `~/.codex/config.toml`:
  57. ```toml
  58. [mcp_servers.nera]
  59. command = "npx"
  60. args = ["-y", "@nera-static/mcp", "--root", "/Users/you/Sites"]
  61. ```
  62. ## What the assistant gets
  63. A **site** is a folder under the root (or the root itself) whose `package.json` depends on `@nera-static/nera`. Tools that work on a site take `site`, its path relative to the root (`.` for the root itself); file tools take a path relative to the site.
  64. ### Tools
  65. | Tool | Does |
  66. | --- | --- |
  67. | `list_starters`, `list_themes`, `list_plugins` | The starter kits, themes and plugins on npm, official ones first; offline, `list_starters` falls back to the official starters |
  68. | `create_site` | Creates a site as `nera new` does (`name`, optional `starter`, `theme`, `title`, `lang`) and installs its packages; returns the starter's first steps as `firstSteps` |
  69. | `list_sites` | The Nera sites under the root |
  70. | `get_site` | A site's configuration, pages, plugins and theme |
  71. | `read_page`, `write_page`, `delete_page` | A Markdown page with its frontmatter; `write_page` refuses frontmatter without `layout` |
  72. | `read_file`, `write_file` | Configuration, templates and assets inside a site |
  73. | `add_plugin` | Installs an official plugin (`@nera-static/plugin-<name>`, `plugin-<name>` or `<name>`) as `nera add` does: the package, its default config and its templates |
  74. | `build` | `nera build`, optionally with the output checks (`check: true`) |
  75. | `validate` | `nera validate`: the site's layouts, includes and YAML, as `{ file, line, severity, rule, message }` records |
  76. | `preview` | Starts `nera dev` and returns the local address; `stop: true` stops it |
  77. | `publish` | `nera publish` to GitHub Pages or Netlify; returns the sign-in code for you, then the live address |
  78. `create_site`, `add_plugin`, `validate` and the catalogs call `@nera-static/nera`'s own functions inside the server; `build`, `preview` and `publish` run commands, through the site's own `@nera-static/nera` when it has one installed, so the assistant gets the same results as you do in a terminal. A preview or a publish keeps running between calls and stops when the client closes the server.
  79. ### Resources
  80. | URI | Holds |
  81. | --- | --- |
  82. | `nera://docs/llms-full.txt` | The complete Nera documentation, bundled with this release |
  83. | `nera://catalog/starters`, `nera://catalog/themes`, `nera://catalog/plugins` | The catalogs as JSON |
  84. | `nera://site/{site}/AGENTS.md` | A site's `AGENTS.md` (`nera://site/AGENTS.md` for a site in the root itself) |
  85. ### Prompts
  86. | Prompt | Walks through |
  87. | --- | --- |
  88. | `new_business_website` | A new business website from the business starter |
  89. | `new_blog` | A new blog from the blog starter |
  90. | `add_page` | Adding a page or a post to a site |
  91. | `put_site_online` | Building, checking and publishing a site |
  92. ## Privacy and safety
  93. - The server only touches files below `--root`. A path outside it is refused with an error, never quietly corrected.
  94. - It never asks for input and never prompts in a terminal; long-running commands run in the background and are stopped when the server exits.
  95. - `publish` signs in through GitHub's device flow: you enter the code in your browser. Tokens stay where `nera publish` keeps them (the system keychain, or a file only you can read) and are never returned to the assistant or written into a site.
  96. - The catalogs are read from the public npm registry (the starters fall back to the official list when it cannot be reached). `create_site` and `add_plugin` install packages from npm. Nothing else leaves your computer unless you publish.
  97. ## Compatibility
  98. - Node.js 22.12 or later
  99. - Brings `@nera-static/nera` 1.27.0 for sites that have none installed. A site with its own CLI installed runs that one: `build` needs 1.9.0 or later (`--json`), `publish` 1.27.0 or later for GitHub Pages and Netlify alike (its sign-in events), and refuses an older one. `npm update` in the site brings it up to date.
  100. ## License
  101. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.