Skip to main content
The MCP server uses OAuth 2.1 for user authentication. When you connect through supported clients, you’re prompted to authorize access via your browser.

API key authentication

For programmatic access or service-to-service authentication, you can use your Kernel API key instead of OAuth. Add your API key to the MCP configuration:
The server automatically detects non-JWT tokens and treats them as API keys. API key authentication is useful for:
  • Automated workflows and CI/CD pipelines
  • Server-to-server integrations
  • Environments where OAuth flows are not practical
API keys bypass the OAuth flow but still require valid Kernel credentials. Keep your API key secure and don’t expose it in client-side code.
If your automation calls the KERNEL API through an SDK instead of the MCP server, it doesn’t need an API key. Use workload identity federation: a CI job or cloud service authenticates with its own identity and gets a credential that expires in minutes. When an MCP client does need a key, scope the key to one project and give it a short expiry.