What is the Nodinite MCP Endpoint?
The Nodinite MCP Endpoint is an IIS-hosted endpoint in Core Services. Its primary use is to support the AI Assistant experience in Nodinite, while also enabling optional access from external MCP clients such as VS Code and similar tools. Starting with Nodinite 7.4.0, Core Services are mandatory, and the MCP Endpoint is part of the technical deployment model for AI-enabled integrations.
From an infrastructure perspective, this endpoint is a web site/application concern in IIS. The MCP Endpoint port is configured in the Nodinite portal during installation and upgrade workflows.
Important
When you install Nodinite 7.4.0 or later, or upgrade from lower versions, you must provide an available MCP Endpoint web site port in the Nodinite portal.
Understanding the Hosting Model
The MCP Endpoint is hosted with Core Services in IIS and serves MCP protocol requests from external clients. The endpoint then reads data from your Nodinite environment through Core Services and the configuration database.
Diagram: IIS hosts the MCP Endpoint, which routes external MCP client requests through Core Services to configuration and repository data.
What This Page Covers
- Technical scope and hosting model for the MCP Endpoint in Core Services
- Port planning requirements for IIS hosting through the Nodinite portal
- Entry points for installation, upgrade, and troubleshooting
- Links to AI pages for client-side MCP configuration and usage guidance
Core Services Responsibilities vs AI Responsibilities
| Area | Core Services documentation | AI documentation |
|---|---|---|
| Focus | IIS hosting, ports, prerequisites, installation, operations | Benefits, usage scenarios, client setup, model/provider configuration |
| Typical reader | Platform engineer, infrastructure administrator | Solution architect, integration analyst, developer |
| Primary pages | Prerequisites, Install MCP Endpoint, Update MCP Endpoint | Set up AI Assistant and MCP Endpoint, MCP Endpoint AI |
VS Code with IIS-hosted MCP Endpoint
Guidance for configuring VS Code specifically against the IIS-hosted MCP Endpoint is coming soon.
Until this section is expanded, use the current MCP client setup guidance in Set up AI Assistant and MCP Endpoint and MCP Endpoint AI.
Frequently Asked Questions
Is MCP Endpoint configuration in AI pages enough for production?
No. AI pages explain client setup and usage. You still need the Core Services technical setup for IIS hosting, port allocation, and runtime operations.
Do I need this when upgrading from older versions?
Yes. If you upgrade from lower versions to 7.4.0 or later, include MCP Endpoint port planning as part of the upgrade execution.