Skip to main content
The Nudj MCP Server connects Nudj features to AI agents through the Model Context Protocol. It runs over Streamable HTTP on port 4010, and exposes a stdio transport for desktop clients.

​
Who this is for

​
Authentication

Every HTTP request to the MCP server requires two headers:
Tokens are minted from Admin Panel → Settings → Developer → MCP Tokens, scoped to your RBAC role (Viewer / Moderator / Manager / Admin / SuperAdmin). The MCP server validates the token and enforces that its claimed organisation matches x-api-domain. See Bearer + Domain Headers for full details. stdio transports (Claude Desktop) use env vars instead of headers.

​
Tool catalog

The MCP server exposes a set of tools categorised by concern. Tool availability is further filtered by the x-agent-mode header — see Agent modes.

​
Nudj platform CRUD

Core domain operations that read and write Nudj data.

​
Shopify

Shop-level integration for Shopify-backed organisations. The Shopify MCP surface includes context injection: the agent starts each session with a pre-fetched snapshot of shop state so it can answer questions without an initial round of API calls.

​
Public web & media

Tools that don’t require Nudj auth. Useful for research and content generation.

​
Docs & events

​
Voice agent

A realtime voice-agent layer sits on top of the MCP tool catalog. Tool availability is filtered to the same x-agent-mode rules; the voice transport itself is a thin shell.

​
Agent modes

The server filters tool access based on the x-agent-mode header, so you can hand a narrower surface to less-trusted agents: If x-agent-mode is omitted, the server defaults to the broadest surface your token’s RBAC role allows.

​
Transports

Serves MCP over Streamable HTTP. All cloud-hosted clients (Claude Code, Cursor, ChatGPT) use this.

​
stdio

Used by Claude Desktop and other native desktop clients that spawn the server as a child process. See MCP Admin Setup for the canonical config.

​
Local development

For contributors working on the MCP server itself:
The TLS bypass is needed because the local Nudj API uses a self-signed cert. All three apps (admin, API, MCP) must share the same NEXTAUTH_SECRET so tokens validate end-to-end. See Claude Code Setup for the full local config.

Admin / Claude Desktop

Admin panel MCP tokens and Claude Desktop stdio config.

Claude Code .mcp.json

Wire up Claude Code with .mcp.json for cloud or local.

Bearer + Domain Headers

The canonical auth pattern for HTTP MCP clients.

Troubleshooting

Diagnose auth, connection, and tool-call issues.