diff --git a/integrations/claude/claude-code-and-desktop.mdx b/integrations/claude/claude-code-and-desktop.mdx index e8401b5e..2d6dcfa3 100644 --- a/integrations/claude/claude-code-and-desktop.mdx +++ b/integrations/claude/claude-code-and-desktop.mdx @@ -3,10 +3,11 @@ title: "Claude Code and Desktop" description: "Give Claude Code and Claude Desktop a Kernel cloud browser" --- -Connect the Claude apps you already use to Kernel. There are two ways to bring Kernel into [Claude Code](https://www.claude.com/product/claude-code): +Connect the Claude apps you already use to Kernel. -- **Marketplace plugin** — load Kernel's skills directly into Claude Code so it knows how to manage cloud browsers and write automations. -- **Remote MCP server** — connect Claude Code to Kernel's [MCP server](/reference/mcp-server) to create and manage cloud browsers from chat. +## Claude Desktop + +Claude Desktop reaches Kernel through Kernel's [official connector](https://claude.ai/directory/kernel), added as a custom connector under **Settings → Connectors**. The [Claude client guide](/reference/mcp-server/clients/claude) has the steps, and covers Claude.ai as well. ## Marketplace plugin (Claude Code) @@ -29,7 +30,7 @@ See the [skills repo](https://github.com/kernel/skills#available-skills) for the ## Remote MCP server (Claude Code) -Add Kernel's remote MCP server to manage cloud browsers from Claude Code. +Add Kernel's [remote MCP server](/reference/mcp-server) to manage cloud browsers from Claude Code. **Using the Kernel CLI (recommended):** @@ -46,7 +47,3 @@ claude mcp add --transport http kernel https://mcp.onkernel.com/mcp # Then in the REPL run once to authenticate: /mcp ``` - -## Claude Desktop - -Claude Desktop reaches Kernel through the same remote MCP server, added as a custom connector under **Settings → Connectors**. The [Claude client guide](/reference/mcp-server/clients/claude) has the steps, and covers Claude.ai as well. diff --git a/integrations/claude/overview.mdx b/integrations/claude/overview.mdx index b660e0eb..a24d6a60 100644 --- a/integrations/claude/overview.mdx +++ b/integrations/claude/overview.mdx @@ -9,7 +9,7 @@ Kernel gives Claude a real, cloud-hosted browser to work in, so your agents can ### Claude Code and Claude Desktop -Connect the Claude apps you already use to Kernel. Add Kernel's [remote MCP server](/reference/mcp-server) to manage cloud browsers from Claude Code or Claude Desktop, or install the [marketplace plugin](https://github.com/kernel/skills#claude-code) to load Kernel's CLI and SDK skills into Claude Code. +Connect the Claude apps you already use to Kernel. Add Kernel's [official connector](https://claude.ai/directory/kernel) to manage cloud browsers from Claude Desktop and Claude.ai, or install the [marketplace plugin](https://github.com/kernel/skills#claude-code) to load Kernel's CLI and SDK skills into Claude Code. [Set up Claude Code and Desktop →](/integrations/claude/claude-code-and-desktop) diff --git a/reference/mcp-server/clients/claude.mdx b/reference/mcp-server/clients/claude.mdx index 5d1c2c97..d67f98ea 100644 --- a/reference/mcp-server/clients/claude.mdx +++ b/reference/mcp-server/clients/claude.mdx @@ -7,10 +7,11 @@ description: "Connect Claude.ai, Claude Desktop, and Claude Code to the Kernel M ## Pro, Max, Team & Enterprise (Claude.ai and Claude Desktop) -1. Go to **Settings → Connectors → Add custom connector**. -2. Enter: **Integration name:** `Kernel`, **Integration URL:** `https://mcp.onkernel.com/mcp`, then click **Add**. -3. In **Settings → Connectors**, click **Connect** next to `Kernel` to launch OAuth and approve. -4. In chat, click **Search and tools** and enable the Kernel tools if needed. +Kernel is available as an [official connector](https://claude.ai/directory/kernel) in the Claude directory. + +1. Open Kernel's [official connector](https://claude.ai/directory/kernel) 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.