Skip to main content
dnz mcp is DNZ’s MCP server for AI assistants that start a command: Claude Desktop, Claude Code, Cursor, VS Code. Assistants that connect to a URL use the server’s /mcp endpoint and sign in with OAuth instead; that endpoint is off until a superadmin turns it on. Client configs and the tool list are in AI assistants (MCP).

Serve over stdio

It reads JSON-RPC on stdin and answers on stdout (notes go to stderr), and talks to the server with the session from dnz login or --token / DNZ_TOKEN, so the tools see and change what that account or token may. History and the audit log show its changes as made through MCP. In an assistant’s config:

Turn the endpoint on

Shows or switches the server’s /mcp endpoint and its OAuth sign-in (superadmins). It is off by default (DNZ_MCP), takes effect at once on every server of a cluster, and turning it off also shuts out the apps already signed in. dnz mcp over stdio doesn’t need it.

Connected apps

apps lists the assistants you allowed at /mcp: their access (read only, or read and change), where they return to after signing in, and when and from where they were last used. revoke signs one out; it has to sign in again. Both need a normal sign-in (dnz login), not an API token. The same list is under Account → Connected apps in the dashboard.