Install MCP Endpoint
This page describes the technical installation flow for the MCP Endpoint hosted in IIS as part of Nodinite Core Services.
Understanding the Installation Scope
The MCP Endpoint is not a separate product package. It is deployed as part of the Core Services installation/update workflow. Starting with 7.4.0, provide a valid, available port for the MCP Endpoint web site in the Nodinite portal during setup.
The primary use of this endpoint is AI Assistant functionality in Nodinite. External MCP client usage is optional and can be enabled after technical deployment.
Installation Steps
Step 1: Confirm prerequisites
Complete all checks from MCP Endpoint Prerequisites.
Step 2: Start Core Services installation/update workflow
Use your standard Nodinite installation method for the target version and environment.
Step 3: Configure MCP Endpoint web site port in the portal
Enter an available TCP port for the MCP Endpoint web site in the Nodinite portal as part of the installation flow.
Important
This step is required for new installs on 7.4.0+ and for upgrades from lower versions.
Step 4: Complete deployment
Finish the Core Services deployment and confirm that the MCP Endpoint site/application is created in IIS.
Step 5: Validate runtime status
Validate these technical outcomes:
- The MCP Endpoint site/application is started in IIS
- The configured port is bound and reachable from approved networks
- No startup errors are present in IIS/Event logs for the endpoint
Step 6: Validate client-level usage
After technical deployment is complete, configure an external MCP client and run a simple query.
For client-side setup, follow:
Upgrade Notes from Lower Versions
When moving from lower versions to 7.4.0 or later:
- Add MCP Endpoint port allocation to your change plan
- Verify firewall and proxy routing for the new endpoint
- Include post-upgrade validation in your deployment checklist