MCP compatibility
MCP authentication
Keep legacy service authorization separate from current REST API keys.
The current REST API authenticates workspace requests with scoped Bearer keys created in Settings → Developer. Those keys do not automatically authorize a legacy MCP service.
An MCP service may advertise OAuth or another supported method. Follow the metadata and authorization flow exposed by that service. Review which account, workspace, and permissions it requests before granting access.
Troubleshooting
- A
401can mean the credential belongs to a different service or has expired. - Missing tools can mean the client has not completed discovery or the service exposes a different tool set.
- An unavailable endpoint can mean the optional compatibility service is not enabled.
Do not put a secret in the connection URL. Use your client's supported secure credential mechanism. For the current REST scopes and key lifecycle, see API authentication.