MCP Server Setup
Configure the Noma MCP server with your personal access token (API key) and project id. The server reads NOMA_API_KEY and NOMA_PROJECT_ID from the environment when your editor starts the process.
Credentials
| Value | Where to find it |
|---|---|
| API key | User Settings → API Keys — with the same workspace selected in the sidebar as the project you’re connecting. Create a key with the abilities you need (see below). |
| Project id | Project home page or Project Settings → API Access (UUID) |
Full access for development
For local AI workflows, many teams enable all abilities on one key (read, create, update, delete, admin) so schema and content tools work without permission errors.
Cursor
Add a server entry to ~/.cursor/mcp.json (create the file if it does not exist):
{
"mcpServers": {
"nomacms": {
"command": "npx",
"args": ["-y", "@nomacms/mcp-server"],
"env": {
"NOMA_API_KEY": "your-api-key",
"NOMA_PROJECT_ID": "your-project-uuid"
}
}
}
}Restart Cursor or reload MCP settings so the new server is picked up.
Claude Code
Register the server with 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-serverMultiple projects
Each MCP entry connects to one Noma project. If projects live in different workspaces, create each API key while that workspace is selected in the dashboard, then use separate keys and env blocks per entry:
{
"mcpServers": {
"nomacms-marketing": {
"command": "npx",
"args": ["-y", "@nomacms/mcp-server"],
"env": {
"NOMA_API_KEY": "marketing-api-key",
"NOMA_PROJECT_ID": "marketing-project-uuid"
}
},
"nomacms-docs": {
"command": "npx",
"args": ["-y", "@nomacms/mcp-server"],
"env": {
"NOMA_API_KEY": "docs-api-key",
"NOMA_PROJECT_ID": "docs-project-uuid"
}
}
}
}API key abilities
The Content API checks abilities on your personal access token. Match them to the tools you rely on (this matches the routes in the Noma API):
| Ability | MCP usage (summary) |
|---|---|
read | get_project; list/get collections; list/get entries; list/get assets |
create | Create entries; upload assets; bulk create entries |
update | Update or patch entries; link entry translations; bulk update entries; bulk update asset metadata |
delete | Delete entries; bulk delete entries; delete assets |
admin | Create/update/reorder/delete collections and fields; all webhook list/get/create/update/delete and logs; add or set default project locales |
Webhook routes use admin only—read alone is not enough to list webhooks.
If the token is valid but lacks the required ability, the API responds with 403.
Related
- MCP Server Overview - What the package does and what it does not expose
- Available Tools - Tool names and MCP resources
- Authentication - Headers, abilities, and error codes for the Content API