MCP Server

The @nomacms/mcp-server package runs a Model Context Protocol (MCP) server over stdio. It connects MCP-compatible clients—such as Cursor, Claude Code, and Windsurf—to your Noma project so an AI agent can manage collections, fields, content entries, assets, and webhooks through structured tool calls instead of only reading documentation.

The server talks to the same Content API as the dashboard and the JavaScript SDK, using your personal access token (API key) and project id from the environment.

What you get

Requirements

• Node.js 18+ (the docs use npx to run the published package)
• NOMA_API_KEY — Create under User Settings → API Keys with the workspace that contains the project selected in the sidebar (keys are scoped per workspace). Grant the abilities your workflows need; many tools require admin for schema work or read / create / update / delete for content and assets. See Setup for a full ability map.
• NOMA_PROJECT_ID — Your project’s UUID from the project home page or Project Settings → API Access

What is not exposed

Removing project locales is not available through MCP (add or set default locales only). For locale removal, use Project settings → Localization in the Noma app. Collection delete is also not exposed as an MCP tool; use the dashboard when you need to remove a collection.

Related

• Setup - Cursor, Claude Code, env vars, and API key abilities
• Available Tools - Full list of tools and MCP resources
• AI Code Editors - How MCP, agent skills, and the SDK fit together
• JavaScript SDK - Runtime client for the app your agent builds
• Authentication - How the Content API validates project-id and bearer tokens