You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kernel is now a preset in Vercel's connector registry, so the connector is created by name instead of by MCP server URL.
What changed
In integrations/vercel/eve-extension.mdx:
Step 2 uses vercel connect create kernel --name kernel-mcp --connection-method mcp / vercel connect attach kernel/kernel-mcp, with a sentence on what the registry entry fills in and why the connection method is explicit.
Every mount snippet uses kernel/kernel-mcp (setup, project layout, connection override).
A Vercel CLI >= 58.8.0 prerequisite — that's where --connection-method landed.
A <Note> that connectors created before the registry entry keep their old UID and keep working.
Kernel's registry entry exposes two connection methods, mcp and api-key, with no default yet, so omitting the flag drops readers into an interactive prompt. Only mcp brokers the per-user OAuth the Connect path is documented around.
Matches the corresponding PRs on kernel/eve-extension and kernel/eve-connect-kernel.
Heads up: the Vercel check fails on this PR, but it fails on every PR in this repo including the last four merged ones — unrelated to these edits. Mintlify deploy and broken-links pass.
Note
Low Risk
Documentation-only changes to integration setup instructions; no runtime or security-sensitive code paths.
Overview
Updates the Eve extension integration guide so Vercel Connect setup follows Kernel’s registry preset instead of creating a connector from the MCP server URL.
Connector creation now uses vercel connect create kernel --name kernel-mcp --connection-method mcp and vercel connect attach kernel/kernel-mcp, with mount/override examples using connect: "kernel/kernel-mcp". The doc adds a Vercel CLI ≥ 58.8.0 prerequisite for --connection-method, dashboard steps that pick MCP in Connectors → Browse all, and a Note that pre-registry connectors (e.g. mcp.onkernel.com/eve-extension) still work unchanged.
Reviewed by Cursor Bugbot for commit 8f4a7af. Bugbot is set up for automated code reviews on this repo. Configure here.
`vercel connect create kernel` pre-fills the MCP URL, auth type, and
branding, and yields a `kernel/<name>` UID. Update the setup commands and
mount snippets, and note that pre-registry connectors keep working.
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.
This automation previously approved commit eccd756 and last assessed 164906e as Very Low. Head is now 533031f. Re-assessed the full base…head diff and the delta since the last assessment.
Delta since last assessment (still docs-only in the same file):
Reformatted the Connect setup explanation from a dense paragraph into a lead-in plus bullets (registry autofill, --connection-method mcp vs api-key, dashboard path, UID confirmation)
Documentation-only MDX updates to Vercel Connect setup commands, CLI version prerequisite, example connect UIDs, and a compatibility note for pre-registry connectors
No runtime code, config, CI, infrastructure, or schema changes
No CODEOWNERS file requiring ownership review
Risk factors checked
Factor
Assessment
Codepaths / blast radius
Docs page only; no production logic
Complexity
Trivial command/string/copy updates in examples
Infra / security
None (docs describe auth setup; no auth code changed)
User-facing surface
Developer docs copy/examples only
Risk change: None — remains Very Low. Approval is not dismissed and is not re-issued.
This automation previously approved commit eccd756 and last assessed 533031f as Very Low. Head is now 1b87705 (merge of main into the PR branch). Re-assessed the full base…head diff and the delta since the last assessment.
Delta since last assessment:
Merge commit only relative to PR intent; net PR diff vs base remains documentation-only in integrations/vercel/eve-extension.mdx
No new production logic, config, CI, or infrastructure changes in the PR’s effective diff
Documentation-only MDX updates: Connect create/attach commands use the registry entry (kernel / kernel-mcp), --connection-method mcp, CLI version prerequisite, example connect UIDs, and a compatibility note for pre-registry connectors
No runtime application code, auth implementation, schema, or infra changes
No CODEOWNERS file requiring ownership review
Risk factors checked
Factor
Assessment
Codepaths / blast radius
Single docs page; no production logic
Complexity
Trivial command/string/copy updates in examples
Infra / security
None (docs describe Connect setup; no auth code changed)
User-facing surface
Developer docs copy/examples only
Risk change: None — remains Very Low. Approval is not dismissed and is not re-issued.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Summary
Kernel is now a preset in Vercel's connector registry, so the connector is created by name instead of by MCP server URL.
What changed
In
integrations/vercel/eve-extension.mdx:vercel connect create kernel --name kernel-mcp --connection-method mcp/vercel connect attach kernel/kernel-mcp, with a sentence on what the registry entry fills in and why the connection method is explicit.kernel/kernel-mcp(setup, project layout, connection override).>= 58.8.0prerequisite — that's where--connection-methodlanded.<Note>that connectors created before the registry entry keep their old UID and keep working.Kernel's registry entry exposes two connection methods,
mcpandapi-key, with no default yet, so omitting the flag drops readers into an interactive prompt. Onlymcpbrokers the per-user OAuth the Connect path is documented around.Matches the corresponding PRs on
kernel/eve-extensionandkernel/eve-connect-kernel.Heads up: the
Vercelcheck fails on this PR, but it fails on every PR in this repo including the last four merged ones — unrelated to these edits. Mintlify deploy and broken-links pass.Note
Low Risk
Documentation-only changes to integration setup instructions; no runtime or security-sensitive code paths.
Overview
Updates the Eve extension integration guide so Vercel Connect setup follows Kernel’s registry preset instead of creating a connector from the MCP server URL.
Connector creation now uses
vercel connect create kernel --name kernel-mcp --connection-method mcpandvercel connect attach kernel/kernel-mcp, with mount/override examples usingconnect: "kernel/kernel-mcp". The doc adds a Vercel CLI ≥ 58.8.0 prerequisite for--connection-method, dashboard steps that pick MCP in Connectors → Browse all, and a Note that pre-registry connectors (e.g.mcp.onkernel.com/eve-extension) still work unchanged.Reviewed by Cursor Bugbot for commit 8f4a7af. Bugbot is set up for automated code reviews on this repo. Configure here.