Link the decision engine to an MCP client by matching the client’s API specification with the engine’s output protocol. You need to update the MCP client’s external integration settings to point to the decision engine’s endpoint and include the correct authentication parameters. Check your environment for prerequisites, such as required runtime dependencies or specific network access rules.
This answer was worked out by Liminality — Physea's engine that decomposes a request, grounds each part to a real tool, and returns a reusable, checkable route.
Connect it over MCP: https://mcp.physea.ai/mcp · physea.ai