Nomacms Mcp Server

Name: Nomacms Mcp Server
Author: NomaCMS

@NomaCMS

代码仓库

关于 Nomacms Mcp Server

MCP server for NomaCMS. Manage collections, fields, content, and assets via AI agents.

#mcp #headless-cms #cms #auth

基本信息

分类

其他

传输方式

stdio

发布者

NomaCMS

提交者

rasitapalak

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Nomacms Mcp Server?

The NomaCMS MCP Server connects AI agents like Cursor and Claude Code to a NomaCMS project, enabling management of collections, fields, content entries, assets, and webhooks through natural language.

How to use Nomacms Mcp Server?

Configure the server with a NOMA_API_KEY (from User settings → API keys) and a NOMA_PROJECT_ID (from the project home page or Project settings → API Access). Add a named MCP entry to your Cursor MCP settings (~/.cursor/mcp.json) or use the Claude Code CLI. Multiple projects can be added as separate MCP entries.

Key features of Nomacms Mcp Server

Connects AI agents to NomaCMS for content management.
Provides 39 tools across collections, fields, entries, assets, and webhooks.
Supports read, create, update, delete, and admin abilities.
Offers three reference resources: field types, collections guide, queries.
Allows multiple projects with separate MCP entries.
Content API supports advanced filtering, pagination, and versioning.

Use cases of Nomacms Mcp Server

Manage collections and fields via natural language.
Create, update, publish, and unpublish content entries programmatically.
Upload and manage assets in bulk.
Configure webhooks and monitor their delivery logs.
Link translations and revert entry versions.

FAQ from Nomacms Mcp Server

What API key abilities are needed for which tools?

Read abilities are needed for list/get operations; create for entries, assets, and webhooks; update for entries, asset metadata, and webhooks; delete for entries, assets, and webhooks; admin for collections, fields, and project locales. The README provides a full table.

Can I work with multiple NomaCMS projects?

Yes, each MCP entry connects to a single project. Add separate entries in your MCP config, each with its own NOMA_API_KEY and NOMA_PROJECT_ID.

How are content entry fields handled?

Fields are custom per collection. Richtext values are markdown strings on write; on read they return either raw markdown or HTML depending on the field’s editor.outputFormat. Relation fields require the related entry’s UUID or numeric ID on write and return nested objects on read.

What resources does the server provide for AI context?

Three resources: nomacms://field-types (16 field types reference), nomacms://collections-guide (best practices), and nomacms://query-reference (full filtering and pagination docs).

Is locale removal exposed through this server?

No. Only adding locales and setting the default locale are available (admin ability). To remove a locale, use the NomaCMS dashboard under Project settings → Localization.