Prerequisites for the Nodinite MCP Endpoint
Before you install or upgrade Nodinite 7.4.0 and later, prepare the IIS hosting environment for the MCP Endpoint. This page focuses on infrastructure readiness, with emphasis on available port planning and Core Services alignment.
Understanding Why Prerequisites Matter
The MCP Endpoint is consumed by external clients, but it is hosted and operated as part of Core Services. If hosting prerequisites are missing, installation can fail or the endpoint can remain unreachable even when other Core Services are healthy.
Technical Checklist
| Verified | Topic |
|---|---|
| IIS role and required web server features are installed | |
| A dedicated, available TCP port is selected in the Nodinite portal for the MCP Endpoint web site | |
| Firewall rules allow inbound traffic to the selected MCP Endpoint port | |
| Service account and app pool identity are valid for your deployment policy | |
| Core Services can connect to the Nodinite Config database | |
| Upgrade plans from lower versions include MCP Endpoint port selection |
IIS and Server Requirements
Use a supported Windows Server and IIS configuration for your Nodinite version. Ensure IIS is operational and that your team can create or bind the MCP Endpoint web site/application during deployment.
For baseline server and IIS requirements, use these Core Services pages:
Port Planning Requirements
Starting with 7.4.0, plan and reserve a port for the MCP Endpoint web site, then configure that port in the Nodinite portal.
New installations
Select an available, approved inbound port and document it in your installation runbook. Configure that same port in the Nodinite portal before executing installation scripts.
Upgrades from lower versions
When upgrading older environments, include MCP Endpoint port selection in the Nodinite portal in the same change window as your Core Services update to avoid partial deployment states.
VS Code with IIS-hosted MCP Endpoint
Detailed guidance for configuring VS Code specifically for the IIS-hosted MCP Endpoint is coming soon.
For current client-side setup guidance, use Set up AI Assistant and MCP Endpoint and MCP Endpoint AI.
Firewall and Access Planning
Open inbound firewall access to the configured MCP Endpoint port from approved client networks. Apply your organization's least-privilege and network segmentation rules.
If your environment uses reverse proxy, WAF, or TLS offloading, validate routing and certificate behavior before go-live.
Configuration Database Reachability
The endpoint relies on the same platform data foundation as other Core Services. Confirm that the environment can reach the Nodinite Config database and that your configured identity can operate according to policy.