MCP server for NomaCMS. Manage collections, fields, content, assets, and webhooks via AI agents.
MCP server for NomaCMS. Manage collections, fields, content, assets, and webhooks via AI agents. That is what the nomacms mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Add this to your Cursor MCP settings (~/.cursor/mcp.json):
Installation goes through your MCP client rather than a global install: point it at @nomacms/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 11 tools. What each one is for:
Ability — Toolsread — list/get collections, entries, assets, webhooks; webhook logscreate — create entries, upload assets, create webhooksupdate — update entries, link_entry_translation, update asset metadata, update webhooksdelete — delete entries, delete assets, delete webhooksadmin — create/update/reorder collections and fields; add/set default project locales (MCP does not expose locale removal)Project — Removing locales is intentionally not exposed here (use Project settings → Localization in the NomaCMS dashboard if you must remove aCollections — The Collections tool exposed by this serverFields — The Fields tool exposed by this serverAssets — The Assets tool exposed by this serverWebhooks — The Webhooks tool exposed by this serverConfiguration is passed through the environment: NOMA_API_KEY, NOMA_PROJECT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. NomaCMS's toolset — Ability, read, create and 8 more — is a fair guide to whether it matches your workflow. It is maintained by NomaCMS; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against NomaCMS's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Ability | Tools |
| read | list/get collections, entries, assets, webhooks; webhook logs |
| create | create entries, upload assets, create webhooks |
| update | update entries, **link_entry_translation**, update asset metadata, update webhooks |
| delete | delete entries, delete assets, delete webhooks |
| admin | create/update/reorder collections and fields; add/set default **project locales** (MCP does not expose locale removal) |
| Project | Removing locales is intentionally **not** exposed here (use **Project settings** → **Localization** in the NomaCMS dashboard if you must remove a locale). |
| Collections | The Collections tool exposed by this server. |
| Fields | The Fields tool exposed by this server. |
| Assets | The Assets tool exposed by this server. |
| Webhooks | The Webhooks tool exposed by this server. |
{
"mcpServers": {
"nomacms": {
"command": "npx",
"args": ["-y", "@nomacms/mcp-server"],
"env": {
"NOMA_API_KEY": "your-api-key",
"NOMA_PROJECT_ID": "your-project-uuid"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NOMA_API_KEY | Credential the server authenticates with. | Yes |
| NOMA_PROJECT_ID | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.