From eccd756a82cf74c76e70be5675c0a5fede9c572a Mon Sep 17 00:00:00 2001 From: dprevoznik <58714078+dprevoznik@users.noreply.github.com> Date: Tue, 4 Aug 2026 19:22:24 +0000 Subject: [PATCH 1/4] Use the Vercel Connect registry entry for the Kernel connector `vercel connect create kernel` pre-fills the MCP URL, auth type, and branding, and yields a `kernel/` UID. Update the setup commands and mount snippets, and note that pre-registry connectors keep working. --- integrations/vercel/eve-extension.mdx | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/integrations/vercel/eve-extension.mdx b/integrations/vercel/eve-extension.mdx index 77b0b81..f908e5e 100644 --- a/integrations/vercel/eve-extension.mdx +++ b/integrations/vercel/eve-extension.mdx @@ -37,11 +37,11 @@ pnpm add @onkernel/eve-extension **2. Create and attach the Kernel connector** in Vercel Connect. Name it `eve-extension` so the mount snippet works unedited: ```bash -vercel connect create mcp.onkernel.com --name eve-extension -vercel connect attach mcp.onkernel.com/eve-extension +vercel connect create kernel --name eve-extension +vercel connect attach kernel/eve-extension ``` -You can also add it from the Vercel dashboard under **Connectors → Browse all → Kernel**. Confirm the UID with `vercel connect list`. +`kernel` is Kernel's entry in Vercel's connector registry, so Vercel fills in the MCP URL, auth type, and branding, then opens your browser for the authorization step. You can also add it from the Vercel dashboard under **Connectors → Browse all → Kernel**. Confirm the UID with `vercel connect list`. **3. Mount the extension** in one line, passing the connector UID: @@ -49,7 +49,7 @@ You can also add it from the Vercel dashboard under **Connectors → Browse all // agent/extensions/kernel.ts import kernel from "@onkernel/eve-extension"; -export default kernel({ connect: "mcp.onkernel.com/eve-extension" }); +export default kernel({ connect: "kernel/eve-extension" }); ``` **4. Run it:** @@ -60,6 +60,10 @@ npx eve dev # or: npx eve deploy Leave `KERNEL_API_KEY` unset. The first time a user drives the browser, Eve surfaces a Connect consent prompt; they approve once and it's cached from then on, persisting across threads and sessions. + + Connectors created before Kernel was in the registry keep working. Leave them as they are and point `connect` at the UID `vercel connect list` prints for them, e.g. `mcp.onkernel.com/eve-extension`. + + ## Included tools and skills Once mounted, the agent has the following tools, namespaced under your mount (e.g. `kernel__browser__*`; discover the exact names via `connection_search`): @@ -150,7 +154,7 @@ Mount the extension as a directory and name the connection file `browser.ts` to ``` agent/extensions/kernel/ - extension.ts # export default kernel({ connect: "mcp.onkernel.com/eve-extension" }) + extension.ts # export default kernel({ connect: "kernel/eve-extension" }) connections/browser.ts # shadows the extension's "browser" connection ``` @@ -163,7 +167,7 @@ import { always } from "eve/tools/approval"; export default defineMcpClientConnection({ url: "https://mcp.onkernel.com/mcp", description: "Kernel cloud browser.", - auth: connect("mcp.onkernel.com/eve-extension"), // or { getToken: async () => ({ token: process.env.KERNEL_API_KEY! }) } + auth: connect("kernel/eve-extension"), // or { getToken: async () => ({ token: process.env.KERNEL_API_KEY! }) } tools: { allow: [ "manage_browsers", From 164906e0ea6ae5841d2913c3af3289d214665b2b Mon Sep 17 00:00:00 2001 From: dprevoznik <58714078+dprevoznik@users.noreply.github.com> Date: Fri, 7 Aug 2026 19:19:42 +0000 Subject: [PATCH 2/4] Select the mcp connection method when creating the Kernel connector Vercel's CLI 58.8.0 adds --connection-method. Kernel's registry entry offers both mcp and api-key, and only mcp brokers the per-user OAuth the extension's Connect path expects. --- integrations/vercel/eve-extension.mdx | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/integrations/vercel/eve-extension.mdx b/integrations/vercel/eve-extension.mdx index f908e5e..652807d 100644 --- a/integrations/vercel/eve-extension.mdx +++ b/integrations/vercel/eve-extension.mdx @@ -19,6 +19,7 @@ You can authenticate through [Vercel Connect](https://vercel.com/connect) or wit npx eve@latest init my-agent && cd my-agent ``` - A [Kernel account](https://dashboard.onkernel.com), with either a Vercel Connect Kernel connector (recommended path below) or a Kernel API key +- For the Connect path, **Vercel CLI `>= 58.8.0`**, which is where `--connection-method` landed. Older CLIs reject the flag. ## Setup with Vercel Connect (recommended) @@ -34,14 +35,14 @@ Vercel Connect is the recommended path because: pnpm add @onkernel/eve-extension ``` -**2. Create and attach the Kernel connector** in Vercel Connect. Name it `eve-extension` so the mount snippet works unedited: +**2. Create and attach the Kernel connector** in Vercel Connect. Name it `kernel-mcp` so the mount snippet works unedited: ```bash -vercel connect create kernel --name eve-extension -vercel connect attach kernel/eve-extension +vercel connect create kernel --name kernel-mcp --connection-method mcp +vercel connect attach kernel/kernel-mcp ``` -`kernel` is Kernel's entry in Vercel's connector registry, so Vercel fills in the MCP URL, auth type, and branding, then opens your browser for the authorization step. You can also add it from the Vercel dashboard under **Connectors → Browse all → Kernel**. Confirm the UID with `vercel connect list`. +`kernel` is Kernel's entry in Vercel's connector registry, so Vercel fills in the MCP URL and branding, then opens your browser for the authorization step. `--connection-method mcp` is the part that matters: the registry entry also offers `api-key`, and only `mcp` gives you the per-user OAuth this extension expects. Omit the flag and the CLI prompts you to choose. You can also add it from the Vercel dashboard under **Connectors → Browse all → Kernel**. Confirm the UID with `vercel connect list`. **3. Mount the extension** in one line, passing the connector UID: @@ -49,7 +50,7 @@ vercel connect attach kernel/eve-extension // agent/extensions/kernel.ts import kernel from "@onkernel/eve-extension"; -export default kernel({ connect: "kernel/eve-extension" }); +export default kernel({ connect: "kernel/kernel-mcp" }); ``` **4. Run it:** @@ -154,7 +155,7 @@ Mount the extension as a directory and name the connection file `browser.ts` to ``` agent/extensions/kernel/ - extension.ts # export default kernel({ connect: "kernel/eve-extension" }) + extension.ts # export default kernel({ connect: "kernel/kernel-mcp" }) connections/browser.ts # shadows the extension's "browser" connection ``` @@ -167,7 +168,7 @@ import { always } from "eve/tools/approval"; export default defineMcpClientConnection({ url: "https://mcp.onkernel.com/mcp", description: "Kernel cloud browser.", - auth: connect("kernel/eve-extension"), // or { getToken: async () => ({ token: process.env.KERNEL_API_KEY! }) } + auth: connect("kernel/kernel-mcp"), // or { getToken: async () => ({ token: process.env.KERNEL_API_KEY! }) } tools: { allow: [ "manage_browsers", From 533031fdede8d2aa8d4b0c881663f1582a7d9e52 Mon Sep 17 00:00:00 2001 From: dprevoznik <58714078+dprevoznik@users.noreply.github.com> Date: Fri, 7 Aug 2026 19:26:40 +0000 Subject: [PATCH 3/4] Break the connector setup notes into bullets --- integrations/vercel/eve-extension.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/integrations/vercel/eve-extension.mdx b/integrations/vercel/eve-extension.mdx index 652807d..0c0cee9 100644 --- a/integrations/vercel/eve-extension.mdx +++ b/integrations/vercel/eve-extension.mdx @@ -42,7 +42,12 @@ vercel connect create kernel --name kernel-mcp --connection-method mcp vercel connect attach kernel/kernel-mcp ``` -`kernel` is Kernel's entry in Vercel's connector registry, so Vercel fills in the MCP URL and branding, then opens your browser for the authorization step. `--connection-method mcp` is the part that matters: the registry entry also offers `api-key`, and only `mcp` gives you the per-user OAuth this extension expects. Omit the flag and the CLI prompts you to choose. You can also add it from the Vercel dashboard under **Connectors → Browse all → Kernel**. Confirm the UID with `vercel connect list`. +`kernel` is Kernel's entry in Vercel's connector registry, so most of the setup is pre-filled: + +- Vercel supplies the MCP URL and branding, then opens your browser for the authorization step. +- `--connection-method mcp` selects the per-user OAuth flow that this extension expects. The registry entry also offers `api-key`, and there is no default yet, so omitting the flag drops you into an interactive prompt. +- To use the dashboard instead of the CLI, add the connector under **Connectors → Browse all → Kernel**. +- Confirm the resulting UID with `vercel connect list`. **3. Mount the extension** in one line, passing the connector UID: From 8f4a7af0ac892683420a0c58133a7d82ee5b5715 Mon Sep 17 00:00:00 2001 From: dprevoznik <58714078+dprevoznik@users.noreply.github.com> Date: Fri, 7 Aug 2026 21:13:05 +0000 Subject: [PATCH 4/4] Link the Connect browse page in the connector setup step --- integrations/vercel/eve-extension.mdx | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/integrations/vercel/eve-extension.mdx b/integrations/vercel/eve-extension.mdx index 7110331..b59746e 100644 --- a/integrations/vercel/eve-extension.mdx +++ b/integrations/vercel/eve-extension.mdx @@ -42,12 +42,7 @@ vercel connect create kernel --name kernel-mcp --connection-method mcp vercel connect attach kernel/kernel-mcp ``` -`kernel` is Kernel's entry in Vercel's connector registry, so most of the setup is pre-filled: - -- Vercel supplies the MCP URL and branding, then opens your browser for the authorization step. -- `--connection-method mcp` selects the per-user OAuth flow that this extension expects. The registry entry also offers `api-key`, and there is no default yet, so omitting the flag drops you into an interactive prompt. -- To use the dashboard instead of the CLI, add the connector under **Connectors → Browse all → Kernel**. -- Confirm the resulting UID with `vercel connect list`. +You can also add it from the Vercel dashboard under [**Connectors → Browse all**](https://vercel.com/onkernel/~/connect/browse): look up "Kernel" and choose **MCP**. Confirm the UID with `vercel connect list`. **3. Mount the extension** in one line, passing the connector UID: