Skip to content

Use the Vercel Connect registry entry for the Kernel connector - #479

Open
dprevoznik wants to merge 1 commit into
mainfrom
hypeship/connect-registry-connector
Open

Use the Vercel Connect registry entry for the Kernel connector#479
dprevoznik wants to merge 1 commit into
mainfrom
hypeship/connect-registry-connector

Conversation

@dprevoznik

@dprevoznik dprevoznik commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Kernel is now an entry in Vercel's connector registry, so vercel connect create kernel resolves the service from the registry instead of requiring the MCP server URL. Vercel pre-fills the MCP URL, auth type, and branding, and the connector gets a kernel/<name> UID.

What changed

In integrations/vercel/eve-extension.mdx:

  • Step 2 uses vercel connect create kernel --name eve-extension / vercel connect attach kernel/eve-extension, with a sentence on what the registry entry fills in.
  • Every mount snippet uses kernel/eve-extension (setup, project layout, connection override).
  • A <Note> that connectors created before the registry entry keep their old UID and keep working.

Matches the corresponding PRs on kernel/eve-extension and kernel/eve-connect-kernel.


Note

Low Risk
Documentation-only changes to integration setup instructions; no runtime or security behavior changes in this repo.

Overview
Updates the Vercel Eve extension setup docs to use Kernel’s Vercel Connect registry entry instead of the legacy MCP hostname.

Connect setup now uses vercel connect create kernel --name eve-extension and vercel connect attach kernel/eve-extension, with a short explanation that kernel pre-fills MCP URL, auth, and branding. All mount and override examples pass connect: "kernel/eve-extension" instead of mcp.onkernel.com/eve-extension.

A Note clarifies that connectors created before the registry entry keep their old UID (e.g. mcp.onkernel.com/eve-extension) and remain valid.

Reviewed by Cursor Bugbot for commit eccd756. 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.
@mintlify

mintlify Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 4, 2026, 7:23 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Aug 4, 2026 7:23pm

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk assessment: Very Low

Verdict: Very Low risk — approved.

Evidence (from diff only)

  • 1 file changed: integrations/vercel/eve-extension.mdx (+10 / −6)
  • Documentation-only MDX updates to Vercel Connect setup commands and example connect UIDs (mcp.onkernel.com/...kernel/...), plus a backward-compatibility note for pre-registry connector UIDs
  • No runtime code, config, CI, auth, infrastructure, or schema changes
  • No CODEOWNERS file requiring additional ownership review
  • No prior approvals on this PR

Risk factors checked

Factor Assessment
Codepaths / blast radius Docs page only; no production logic
Complexity Trivial string/command updates in examples
Infra / security None
User-facing surface Developer docs copy/examples only

Safe to approve under the Very Low criteria (documentation-only, small scoped diff, no shared systems or production behavior change).

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant