Official Noma MCP server

Published package: @nomacms/mcp-server. Most teams invoke it through npx -y so everyone stays on a recent build without global installs.

Required environment variables:

• NOMA_API_KEY — user API key from User settings → API keys
• NOMA_PROJECT_ID — UUID from the project home or Project settings → API access

Example (Cursor-flavored JSON):

{
  "mcpServers": {
    "nomacms": {
      "command": "npx",
      "args": ["-y", "@nomacms/mcp-server"],
      "env": {
        "NOMA_API_KEY": "your-api-key",
        "NOMA_PROJECT_ID": "your-project-uuid"
      }
    }
  }
}

The package registers 39 tools (see Available tools). Groupings include:

• Project — locales, defaults, metadata your agent needs before writing content.
• Collections & fields — create or reorder schema when you use an admin-capable key.
• Entries — list, filter, create, patch, publish, unpublish, delete, bulk helpers, translation linking, and version list, get, revert, and label updates.
• Assets — upload, bulk upload, metadata updates, deletes.
• Webhooks — create integrations and inspect delivery logs.

Each entry surfaces custom fields under a fields object; relation writes expect related entry ids, not nested objects. Richtext honors each field’s markdown vs HTML output configuration.

Agents can fetch these without leaving MCP:

• nomacms://field-types
• nomacms://collections-guide
• nomacms://query-reference

Point models at them when you need authoritative filter operators, pagination, or validation notes.

Match keys to the tools you enable:

• read — list/get collections, entries, assets, webhooks, logs
• create — new entries, uploads, webhooks
• update — entry updates, translation linking, metadata, webhook edits
• delete — destructive entry/asset/webhook operations
• admin — schema mutations and locale management exposed via MCP

• GitHub — NomaCMS/nomacms-mcp-server
• MCP feature overview on nomacms.com
• Agent hub (Cursor, Claude Code, Codex, more)