Remote MCP integrations

If you add a new custom integration and define the Remote MCP URL, an MCP integration will be created. Next choose the right API authentication configuration - by default this is set as OAUTH2. You only need to change this if the remote MCP has api token auth or no auth. ## MCP Tool Discovery Tool discovery is based on the auth type and will be visible in the MCP Tools tab. NONE - if no authentication is required, the tools will be discovered once the authentication configuration is saved. API_TOKEN - tools will also be discovered upon saving the api key.

OAUTH2 - since tool discovery requires OAuth authentication, then the discovered tools will only become visible once the first authentication has been successfully completed, either by pre-authing a user under Integration Users or by starting a run and finishing the OAuth consent flow. NB! For token refreshing to work, the correct token url must be configured under API authentication configuration. The default will be the same host that is used for the authorization flow with /token appended. But this can vary based on the MCP provider.