Troubleshooting MCP Endpoint

Use this troubleshooting guide when the MCP Endpoint is hosted in IIS through Core Services and external clients cannot connect or query data.

Diagnostic Approach

Troubleshoot in this order:

1. IIS site/application health
2. Port binding and network reachability
3. Firewall and proxy routing
4. Upgrade configuration completeness
5. External MCP client configuration

Common Issues

The MCP Endpoint site does not start in IIS

Validate app pool identity, binding configuration, and event log errors. Confirm that no other service already owns the configured port.

The endpoint port is unreachable

Confirm inbound firewall rules and routing policy for the selected MCP Endpoint port. Test from the same network segments used by your MCP clients.

Upgrade completed, but MCP requests fail

Re-check that the upgrade included MCP Endpoint port setup in the Nodinite portal and that IIS bindings were retained after update.

I need to remove MCP Endpoint from this environment

Use the standard uninstall script flow and follow Uninstall MCP Endpoint.

External client can load but returns no usable response

If technical endpoint checks pass, move to client configuration checks in AI documentation:

• Set up AI Assistant and MCP Endpoint
• MCP Endpoint AI

Next Step

• MCP Endpoint Prerequisites
• Install MCP Endpoint
• Update MCP Endpoint
• Uninstall MCP Endpoint

Related Topics

• MCP Endpoint Overview
• Core Services
• Set up AI Assistant and MCP Endpoint
• MCP Endpoint AI