Skip to main content
Our remote MCP server isn’t compatible with the method Free users of Claude use to add MCP servers.

​
Pro, Max, Team & Enterprise (Claude.ai and Claude Desktop)

Kernel is available as an official connector in the Claude directory.
  1. Open Kernel’s official connector and click Connect (or find Kernel under Settings → Connectors).
  2. Launch OAuth and approve.
  3. In chat, click Search and tools and enable the Kernel tools if needed.
On Claude for Work (Team/Enterprise), only Primary Owners or Owners can enable custom connectors for the org. After it’s configured, each user still needs to go to Settings → Connectors and click Connect to authorize it for their account.

​
Existing Claude Desktop CLI setups

If you connected Claude Desktop with kernel mcp install --target claude, rerun the command with the latest Kernel CLI and authorize again. By default, the updated config gives Claude Desktop its own mcp-remote auth cache, so the consent screen names Claude Desktop. If you already set MCP_REMOTE_CONFIG_DIR in the server’s env, choose a separate directory for Claude Desktop yourself. Each client needs a separate OAuth callback port as well as a separate cache to authorize while other clients are running. The CLI uses 46093 for Claude Desktop and preserves an existing explicit port. If you customize it, choose an unused port that no other client uses. For a manual mcp-remote setup, add 46093 immediately after the server URL, then add --static-oauth-client-metadata followed by {"client_name":"Claude Desktop"} to the server’s arguments, and set MCP_REMOTE_CONFIG_DIR in its env to an absolute directory dedicated to Claude Desktop. If the old registration still shows MCP CLI Proxy, close Claude Desktop, remove the cache it used (~/.mcp-auth/mcp-remote-v1/ by default, or mcp-remote-v1/ under your custom MCP_REMOTE_CONFIG_DIR), then reopen Claude Desktop and authorize again. This also signs out other clients using that cache.

​
Claude Code CLI

Using Kernel CLI (recommended):
Manual setup: