@nera-static/mcp
Supports GitHub device-flow authentication for publishing Nera sites; the user enters a code in the browser, and tokens stay in the system keychain or a private file rather than being exposed to the assistant.
Publishes Nera sites to GitHub Pages via nera publish and returns the live site address.
Publishes Nera sites to Netlify via nera publish and returns the live site address.
Reads starter-kit, theme, and plugin catalogs from the public npm registry and exposes them as tools and JSON resources.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@nera-static/mcp
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 Nera sites in one folder on your computer, and nowhere else.
📖 Documentation: nera.js.org
npx -y @nera-static/mcp --root ~/SitesThe 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).
Requirements
Node.js 22.12 or later (
node --version), withnpx. Not needed for the Claude Desktop extension, which brings its own.For
publish: a GitHub account (and a Netlify account if you host there)
Related MCP server: DMCPS
Install
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.
Download
nera-mcp-<version>.mcpbfrom the latest release.Double-click it and choose Install in Claude Desktop.
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@neraor, inside Claude Code 2.1.275 or later, in one step:
/plugin install nera --marketplace seebaermichi/nera-mcpClaude 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/SitesAdd --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/Sitesor in ~/.codex/config.toml:
[mcp_servers.nera]
command = "npx"
args = ["-y", "@nera-static/mcp", "--root", "/Users/you/Sites"]What the assistant gets
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.
Tools
Tool | Does |
| The starter kits, themes and plugins on npm, official ones first; offline, |
| Creates a site as |
| The Nera sites under the root |
| A site's configuration, pages, plugins and theme |
| A Markdown page with its frontmatter; |
| Configuration, templates and assets inside a site |
| Installs an official plugin ( |
|
|
|
|
| Starts |
|
|
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.
Resources
URI | Holds |
| The complete Nera documentation, bundled with this release |
| The catalogs as JSON |
| A site's |
Prompts
Prompt | Walks through |
| A new business website from the business starter |
| A new blog from the blog starter |
| Adding a page or a post to a site |
| Building, checking and publishing a site |
Privacy and safety
The server only touches files below
--root. A path outside it is refused with an error, never quietly corrected.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.
publishsigns in through GitHub's device flow: you enter the code in your browser. Tokens stay wherenera publishkeeps them (the system keychain, or a file only you can read) and are never returned to the assistant or written into a site.The catalogs are read from the public npm registry (the starters fall back to the official list when it cannot be reached).
create_siteandadd_plugininstall packages from npm. Nothing else leaves your computer unless you publish.
Compatibility
Node.js 22.12 or later
Brings
@nera-static/nera1.27.0 for sites that have none installed. A site with its own CLI installed runs that one:buildneeds 1.9.0 or later (--json),publish1.27.0 or later for GitHub Pages and Netlify alike (its sign-in events), and refuses an older one.npm updatein the site brings it up to date.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Let your AI agent build, preview and update web apps, download source and publish when you allow it.
Build, version, review, and export websites, web apps, and games from a conversation.
Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback.
Host websites and data for AI agents: build pages, tables and actions, then publish.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely read, write, and list files and run shell commands inside dashboard-whitelisted sandbox directories. It provides API-key authentication, firewall controls, and preinstalled development tools for connecting MCP-compatible clients.1Business Source 1.1
- FlicenseNot gradedqualityBmaintenanceTurns web-based AI chat clients into secure operators of a local machine by exposing a governed, OAuth-gated set of 38 tools for file read/write/edit, whitelisted shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost/LAN fetching, clipboard, notifications, ports, Postman, and AIObox windows. Access is confined to user-approved folders with a strict command whitelist, rate limits, and a security log.-
- AlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 tools over a single OAuth-gated MCP endpoint, letting web-based AI chat clients read and edit local files, run whitelisted shell commands, search, use Git, inspect SQLite databases, and drive browser, DevTools, clipboard, and background-task workflows. It requires no system-wide install or admin rights and restricts access to folders and commands approved from a local control panel.MIT