OAuth 2.1
For AI desktop applications like Claude Desktop or Cursor, the MCP Server supports OAuth 2.1 with PKCE. The application opens a browser window where you log in with your Nekt credentials (or SSO), select which token to use, and the app receives access automatically. No manual token copying is needed. To connect, point your AI application to your MCP server URL using the HTTP Streamable transport protocol.Bearer Token
For automation platforms like N8N, Make, or custom integrations, you can use a bearer token directly. Copy the token from the Nekt platform and paste it into your tool’s configuration. Tokens can also be minted and managed from the Platform API with an API key — useful when provisioning an agent is part of a script rather than a one-off. The secret itself is never returned to the script: the response carries a one-time link that opens in the creating user’s browser, so a person still collects and pastes it.Tokens created during the OAuth flow use the creating user’s permissions by
default. Tokens created manually can be scoped to specific tables for
fine-grained access control.