add_project_locale
Add a locale code (e.g. tr, es) to the project. Requires admin API ability. Codes are lowercased. Call when setting up a multilingual site before creating translated content.
LABSCO SUMMARY
Saving and publishing are separate events here, and the public API keeps serving the old snapshot until you say otherwise.
update_entry, patch_entry and bulk_update_entries all state the same thing: a save never moves the publish pointer, so reads at state=published keep returning the last minted version until publish_entry runs. That makes staged editing the default rather than something you build, and it makes publish_entry the call that actually ships. There are edges worth knowing before you automate against it. A translation group can be created through link_entry_translation but not split — undoing one is a dashboard action, not an API call. And the bulk tools are all-or-nothing by design, which is what you want for a migration and is worth remembering when a single malformed row stops the batch.
What it is
The official MCP server for a NomaCMS project, exposing 39 tools that cover the content model, entries and their draft and published versions, translation groups, assets and webhooks.
What you get
- The content model itself, not only its contents: create_collection can carry its full field schema in the same request, create_field and update_field set type, options, validations, label and placeholder, and reorder_collections and reorder_fields control display order.
- Reads that come back shaped for use: get_entry returns a fields object with relation fields already expanded into nested entry objects or arrays rather than bare UUIDs, and list_entries takes a where expression alongside sort, state, locale and pagination.
- Writes split by intent: update_entry replaces the whole entry over HTTP PUT and needs the required fields present, while patch_entry changes only the keys you send.
- Publication as its own step: publish_entry mints an immutable version and resets is_draft_dirty, unpublish_entry clears the live pointer while keeping every historical version, and delete_entry is a soft delete recoverable from the admin panel.
- A version history you can read and walk back into: list_entry_versions returns version_number, label, description, published_at, created_by and is_current_published, get_entry_version returns the raw snapshot payload, revert_entry_version restores a snapshot into the draft and publishes it as a new version, and update_entry_version_label renames a version without touching its snapshot.
- Atomic bulk operations: bulk_create_entries, bulk_update_entries, bulk_delete_entries, bulk_upload_assets and bulk_update_asset_metadata each roll the whole request back if a single item fails.
- Multilingual structure: add_project_locale and set_default_project_locale manage the project's locale list, and link_entry_translation merges entries in different locales into one translation group.
- Assets and delivery hooks: upload_asset takes an absolute path, get_asset resolves by UUID or by filename, and create_webhook binds content and auth events to a URL with a secret, a payload, source filters and specific collection_ids, with list_webhook_logs showing what was delivered.
Requirements
A NomaCMS project API key and the project it addresses, supplied as NOMA_API_KEY and NOMA_PROJECT_ID. Changing the project's locales needs a key carrying admin ability, and link_entry_translation needs one carrying update ability, so a read-and-write key alone will not cover the whole tool set.
Setup effort
One command plus a key — npx -y @nomacms/mcp-server, then supply credentials
USE CASES
01
Standing up a content model from scratch
Create the collection with its fields in the same request, add the ones you missed, and put them in the order an editor should meet them.
02
Editing live content without changing what readers see
Send only the keys that changed, confirm the draft reads back the way you meant, and mint the new version when it is ready to go out.
03
Rolling back a page that shipped wrong
Read the version list to find the last good snapshot, check its payload before committing to it, and restore it as a new published version.
04
Migrating a batch of records in one shot
Write the rows atomically so a bad one leaves nothing behind, correct them in place, and read the collection back with a filter to confirm the shape.
05
Taking an existing site multilingual
Register the locale on the project, decide which one is the default, and tie the translated entry to the original so they travel as one.
06
Telling a build when an editor publishes
Bind the events you care about to a URL with a shared secret, scope it to the collections that matter, and read the delivery log when a build does not fire.
39 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
bulk_create_entries
Create multiple content entries atomically. If one item fails, the whole request is rolled back.
bulk_delete_entries
Delete multiple content entries atomically by UUID. If one delete fails, no entries are deleted.
bulk_update_asset_metadata
Update metadata for multiple assets atomically by UUID. If one item fails, all updates are rolled back.
bulk_update_entries
Update multiple content entries atomically by UUID. If one item fails, all updates are rolled back. Saves never change publish state — call publish_entry per UUID to mint new versions after bulk updates.
bulk_upload_assets
Upload multiple local files as assets atomically. If one upload fails, all uploads are rolled back.
create_collection
Create a new collection. Optionally include field definitions to create the collection with its full schema in a single request.
create_entry
Create a new content entry in a collection
create_field
Add a new field to a collection
create_webhook
Create a webhook for content and auth events
delete_asset
Delete an asset by UUID
delete_entry
Soft-delete a content entry (moves to trash). Can be restored from the admin panel.
delete_webhook
Delete a webhook by UUID
get_asset
Get an asset by its UUID or by filename.
get_collection
Get a single collection with its full field schema by slug
get_entry
Get a single content entry by UUID. Response includes uuid, locale, published_at, and a fields object (custom field values — not a nested data key). Relation fields appear as nested entry objects (one-to-one) or arrays of entries (one-to-many), not as bare UUIDs.
get_entry_version
Fetch a single version's metadata and raw snapshot payload. The snapshot contains the saved field values in restoration format; for API-rendered content use get_entry with state='published'.
get_project
Get information about the current Noma project (name, uuid, default_locale, locales, etc.)
get_webhook
Get a webhook by UUID
link_entry_translation
Merge two entries in the same collection into one translation group (same as dashboard “link translation”). Both entries must exist, belong to this collection, and have different locales. There is no unlink via API — use the dashboard if you need to split a group. Requires an API key with update ability.
list_assets
List assets in the project with optional pagination.
list_collections
List all collections in the project
list_entries
List content entries for a collection with advanced filtering, sorting, and pagination. Use the 'where' parameter for powerful queries. Read the 'query-reference' resource for full documentation on operators and examples.
list_entry_versions
List all published versions for a content entry (newest first). Each version is an immutable snapshot taken at publish time. Response includes version_number, label, description, published_at, created_by, and is_current_published for each version.
list_webhook_logs
List delivery logs for a webhook
list_webhooks
List all webhooks configured for the current project
patch_entry
Partially update a content entry (HTTP PATCH). Only include fields you want to change (e.g. relations, one field). Saves NEVER change the publish state — call publish_entry explicitly to mint a new version. Prefer this over update_entry when you are not replacing the entire entry.
publish_entry
Mint a new immutable version from the entry's current draft and make it the live published version. After this call, state=published reads from the public API will return the new snapshot and is_draft_dirty is reset to false.
reorder_collections
Update the display order of collections
reorder_fields
Update the display order of fields within a collection
revert_entry_version
Restore the draft to a previous version's snapshot and publish it as a new version. The current unpublished draft is replaced. Returns the new version number.
set_default_project_locale
Set the project's default locale. Adds the locale to the list if it was missing. Requires admin API ability.
unpublish_entry
Clear the live published pointer for an entry. The entry becomes invisible under state=published in the public API, but all historical versions are retained and still accessible via list_entry_versions / get_entry_version.
update_collection
Update the name and slug of an existing collection
update_entry
Replace an existing content entry (HTTP PUT). Sends the full data payload; required fields (e.g. title, slug) must be included. Saves NEVER change the publish state — if the entry has a published version, the public API keeps serving that snapshot under state=published until you explicitly call publish_entry. Use patch_entry for partial updates and publish_entry/unpublish_entry to control visibility.
update_entry_version_label
Update a version's editable label and/or description. The snapshot payload itself is immutable.
update_field
Update an existing field on a collection
update_webhook
Update a webhook by UUID
upload_asset
Upload a local file as an asset. Provide the absolute file path.
BEFORE YOU INSTALL
What to know first
Tools you get
39 tools when we connected. Removing a project locale is dashboard-only. Abilities are per key: without admin you cannot create collections or fields, and without delete you cannot delete entries, assets or webhooks.
Requires
- npx on PATH
- NOMA_API_KEY in your environment
- NOMA_PROJECT_ID in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 39 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @nomacms/mcp-serverMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"nomacms": {
"command": "npx",
"args": [
"-y",
"@nomacms/mcp-server"
],
"env": {
"NOMA_API_KEY": "<YOUR_NOMA_API_KEY>",
"NOMA_PROJECT_ID": "<YOUR_NOMA_PROJECT_ID>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add nomacms -e NOMA_API_KEY=<YOUR_NOMA_API_KEY> -e NOMA_PROJECT_ID=<YOUR_NOMA_PROJECT_ID> -- npx -y @nomacms/mcp-server
