NomaCMS MCP Server
About
MCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.
Details
- Author
- nomacms
- Categories
- Developer Tools, Other, Automation
Jump to
Setup
Install NomaCMS MCP Server in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/nomacms/nomacms-mcp-server
Follow the installation instructions in the repository README, then restart your MCP client.
MCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.
An MCP (Model Context Protocol) server that connects AI agents likeCursorandClaude Codeto your NomaCMS project. Manage collections, fields, content entries, assets, and webhooks programmatically through natural language.
- NOMA_API_KEY: API key fromUser settings → API keys— seeAPI key abilities.
- NOMA_PROJECT_ID: Your project's UUID — you can find it on the project home page or underProject settings → API Access
Add this to your Cursor MCP settings (~/.cursor/mcp.json):
{ "mcpServers": { "nomacms": { "command": "npx", "args": ["-y", "@nomacms/mcp-server"], "env": { "NOMA_API_KEY": "your-api-key", "NOMA_PROJECT_ID": "your-project-uuid" } } } }
Add the MCP server using the Claude Code CLI:
claude mcp add nomacms \ -e NOMA_API_KEY=your-api-key \ -e NOMA_PROJECT_ID=your-project-uuid \ -- npx -y @nomacms/mcp-server
- get_project— Get project information (default_locale,locales, etc.)
- add_project_locale— Add a locale code to the project (requiresadmin)
- set_default_project_locale— Set the default locale (requiresadmin)
Removing locales is intentionallynotexposed here (useProject settings→Localizationin the NomaCMS dashboard if you must remove a locale).
- list_collections— List all collections
- get_collection— Get a collection with its full field schema
- create_collection— Create a collection (with optional batch field creation)
- update_collection— Update a collection's name and slug
- reorder_collections— Reorder collections
- create_field— Add a field to a collection
- update_field— Update a field
- reorder_fields— Reorder fields within a collection
- list_entries— List entries with advanced filtering (wherewith 13 operators, OR groups, relation filtering), sorting, pagination, count, and first
- get_entry— Get a single content entry
- create_entry— Create a content entry
- update_entry— Update a content entry
- patch_entry— Partially update an entry (HTTP PATCH; merge only the fields you send)
- publish_entry— Publish the draft as a new immutable version (update)
- unpublish_entry— Clear the live published pointer; versions retained (update)
- delete_entry— Soft-delete a content entry (moves to trash)
- bulk_create_entries— Create multiple entries atomically
- bulk_update_entries— Update multiple entries atomically by UUID
- bulk_delete_entries— Delete multiple entries atomically by UUID
- link_entry_translation— Link two entries (different locales) into the same translation group (POST …/link-translation; requiresupdateability)
- list_entry_versions— List version history for an entry
- get_entry_version— Fetch one version by number (includes snapshot payload)
- revert_entry_version— Restore draft from a prior snapshot and publish (update)
- update_entry_version_label— Edit label/description on a version; snapshot unchanged (update)
Content API shape:Each entry hasuuid,locale,published_at, andfields(custom field values). Richtext values aremarkdown stringson write; on read they are either raw markdown or rendered HTML depending on the field’seditor.outputFormat(markdownvshtml).Relation fieldsreturn nested entry objects (or arrays for one-to-many) on read; on write send only the related entry’sUUIDornumeric id(never the full nested object from a previousget_entry).get_entrysupportstranslation_locale,exclude,timestamps, andstatequery parameters.
Asset URLs:The API returnsurl,thumbnail_url, andoriginal_urlas stable links (optional?variant=thumbnailor?variant=original).
- list_assets— List assets with pagination
- get_asset— Get an asset by UUID or filename
- upload_asset— Upload a file as an asset
- bulk_upload_assets— Upload multiple files atomically
- bulk_update_asset_metadata— Update metadata for multiple assets atomically
- delete_asset— Delete an asset
- list_webhooks— List all webhooks for the project
- get_webhook— Get a webhook by UUID
- create_webhook— Create a webhook for content and auth events (name,url,events,sources; optionaldescription,secret,payload,status,collection_ids)
- update_webhook— Update a webhook by UUID (same fields as create)
- delete_webhook— Delete a webhook by UUID
- list_webhook_logs— List delivery logs for a webhook (uuid; optionalpaginate,page)
The server exposes three reference resources that AI agents can read for context:
- Field Types Reference(nomacms://field-types) — Complete reference of all 16 field types, their options, validations, and common patterns.
- Collections Guide(nomacms://collections-guide) — Guide for working with collections, singletons, reserved slugs, and best practices.
- Query Reference(nomacms://query-reference) — Full documentation for content queries:wherefilters with 13 operators, OR groups, relation filtering, sorting, pagination, and examples.
Your API key needs the appropriate abilities for the tools you want to use:
Create the key in the NomaCMS dashboard underUser settings → API keys. Copy theProject IDfrom the project home page orProject settings → API Accesswhen you configure this server.
Each MCP entry connects to a single NomaCMS project. To work with multiple projects, add separate entries in your MCP config:
{ "mcpServers": { "nomacms-blog": { "command": "npx", "args": ["-y", "@nomacms/mcp-server"], "env": { "NOMA_API_KEY": "blog-project-api-key", "NOMA_PROJECT_ID": "blog-project-uuid" } }, "nomacms-store": { "command": "npx", "args": ["-y", "@nomacms/mcp-server"], "env": { "NOMA_API_KEY": "store-project-api-key", "NOMA_PROJECT_ID": "store-project-uuid" } } } }
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Connect Cursor, Claude Code, or any MCP-compatible tool directly to your ElmapiCMS instance. Manage collections, content, and assets through natural language.
Manage your Storyblok CMS using natural language through AI tools.
MCP server for WordPress: connect Claude, ChatGPT, Cursor, and other AI clients to manage content, edit themes, run WP-CLI, and automate self-hosted WordPress sites.
Manage and utilize website content within the DevHub CMS platform
A server for integrating with WordPress sites, enabling content management and interaction via the Model Context Protocol.
Extract, govern, and ship structured content from your codebase.
This server enables AI assistants and other MCP clients to interact with Directus instances programmatically.
Agency-grade MCP server for WordPress Elementor — multi-site fleet management, safe page/widget-level editing, template export/import, version tracking with snapshot/rollback.
An MCP server for WordPress and Elementor, enabling AI assistants to manage content and build pages.
Localization as code — 7 MCP tools to push, pull, translate, extract strings, and search translations. AI-powered, type-safe, 182 languages.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


