Troubleshooting
Resolve connection, executable-path and contract lookup problems.
Troubleshooting
Server does not start: check Node’s version and executable path, use npx.cmd where needed, or install the archive locally. The first download needs network access.
OutSystems asks for a session token: renew it through the existing OutSystems MCP and Service Studio approval flow. Never paste it into the BluKavantUI configuration.
A contract is missing: search the catalog and check platform, edition and snapshot version. The server reports unavailable combinations rather than substituting another API.
Continue from the right place
For a native binding issue, follow the OutSystems workflow and compare the documented producer type with the one referenced by your consumer.