- 3 minutes to read

Install MCP Endpoint

The MCP Endpoint is not a separate package. The Nodinite Portal adds it to every Nodinite 7.4.0 or later environment as the MCP Server, and the generated installation package deploys it together with the other Core Services. This page lists what is specific to the MCP Endpoint; the full procedure is Install Nodinite v7.

Installation Steps

Step 1: Confirm prerequisites

Complete the checklist in MCP Endpoint Prerequisites: port, firewall, TLS certificate, service identity, and, for remote clients, a Microsoft Entra ID app registration.

Step 2: Enter the MCP Server values in the Portal

In the Nodinite Portal, open the environment and enter:

Portal step MCP Server value
Auth → MCP Server (OAuth only) MCP Server Audiences and Web Client MCP Server Scope
Servers → Core host Configuration TLS host name and certificate subject, shared by all Core Services
Servers → Core platform services A free port for the MCP Server, and its identity when you don't use one account for all services
Servers → Core platform services Keep the MCP Server stopped: clear it to start the endpoint after installation; select it to deploy the endpoint but leave it stopped

Important

The MCP Server port is required for new 7.4.0+ installations and for updates from older versions.

Step 3: Review and download the package

Check the port under Review and Download → Allocated ports, then download the ZIP file.

Step 4: Run the generated package

Run Nodinite.Installer.Cli.exe from an elevated PowerShell 7 prompt, as described in Run the CLI Workflow. The installer creates the MCP Endpoint web site, binding, and app pool in IIS, together with the other Core Services.

Step 5: Verify the endpoint

Check these outcomes on the Core Services host:

  • The MCP Endpoint web site and app pool are started in IIS. If Keep the MCP Server stopped is selected in the Portal, the app pool stays stopped by design; clear the option and run the package again to start it.
  • The port is bound and reachable from the client networks you approved.
  • The Windows Application event log shows no startup errors for the site. An IIS 500.30 error usually means invalid startup configuration.
  • In OAuth mode, https://nodinite.contoso.com:<port>/.well-known/oauth-protected-resource returns the canonical resource URL and your Entra ID tenant; see Verifying a Deployment.

Step 6: Connect a client

After the technical checks pass, connect a client and ask a simple question, such as List my Nodinite monitor views:

Next Steps