Update MCP Endpoint
The MCP Endpoint is updated together with the other Core Services when you run the update package from the Nodinite Portal; you never update it on its own. Follow Update Nodinite v7 for the procedure, and use this page for what is specific to the MCP Endpoint.
Update Checklist
- In the Nodinite Portal, check the MCP Server port and identity under Servers → Core platform services, and the firewall rule for that port.
- If TLS is used, check that a valid certificate matching the subject under Servers → Core host Configuration is installed on the server; the update finds it and binds it again.
- Download and run the update package as described in Update Nodinite v7. If the installer reports locked files, see File Locks Detected.
- After the update, check that the MCP Endpoint web site is started and reachable, as in Verify the endpoint.
- Ask one question from the AI Assistant or an external MCP client to confirm that the tools load.
The update keeps the Keep the MCP Server stopped setting from the Portal. If the MCP Endpoint is stopped after an update, check that option first: when it is selected, the installer leaves the application pool stopped. To start the endpoint, clear the option under Servers → Core platform services, download the package again, and run the update.
Version Transition Notes
Updating from a version before 7.4.0
The environment has no MCP Server yet. Enter a free port for the MCP Server in the Portal before you download the update package, and open the firewall for it in the same change. For OAuth installations, also enter the values under Auth → MCP Server. Then follow Install MCP Endpoint from step 5.
Monthly updates on 7.4.0 and later
Keep the same port and host name. MCP clients and the AI Assistant depend on the canonical URL; if you change the port, host, or certificate name, update Mcp:ResourceUrl and every client configuration, as described in Choose One Canonical URL.
Clients that run the Nodinite.Core.McpServer NuGet package locally pin a package version in their own mcp.json. Move them to the version that matches the environment; see Tune the values for your environment.