About this integration
MCP server for NomaCMS. Manage collections, fields, content, assets, and webhooks via AI agents.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.2.2
- Package
- @nomacms/mcp-server
- Last compatibility test
- Not independently tested
Connect your agent
@nomacms/mcp-serverPublisher README and npm manifest document the executable, project-scoped API-key configuration, and tools. The package and NomaCMS API were not executed or independently security-audited; granted API-key abilities determine available operations.
Capabilities: Manage CMS collections and fields, Create, update, publish, and version content, Manage assets, Manage webhooks
Connected profiles
Additional details
io.github.NomaCMS/nomacms-mcp-server
Source ↗ · Checked 2026-09-171.2.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17NOMA_API_KEY, NOMA_PROJECT_ID
Source ↗ · Checked 2026-09-17@nomacms/mcp-server
Source ↗ · Checked 2026-09-191.2.2
Source ↗ · Checked 2026-09-19The publisher documents launching the package as a local MCP command with credentials supplied in the client configuration, without an interactive login step at server startup.
Source ↗ · Checked 2026-09-19A NomaCMS API key and project UUID are required; the API key must be provisioned with the abilities needed by the selected tools.
Source ↗ · Checked 2026-09-19The MCP client starts npx with @nomacms/mcp-server and supplies NOMA_API_KEY and NOMA_PROJECT_ID through the process environment for one project.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19