Expose Config Registry recommendations through MCP

[masnwilliams]

Summary

• add a project-aware resolve_browser_config MCP tool for cached lookup, analysis start, and analysis polling
• return browser, proxy, evidence, and guidance responses without reshaping the SDK contract
• document and register the new toolset with focused MCP contract tests

Why

Browser agents should consult Config Registry before creating a session so cached recommendations return immediately and missing recommendations can be analyzed before the target flow begins.

Testing

• bun test (607 passed)
• bunx tsc --noEmit
• focused Prettier check on changed files
• bun run build compiled and typechecked successfully, then stopped during page-data collection because KERNEL_CLI_PROD_CLIENT_ID is unavailable locally

---

Note

Medium Risk
Exposes a new authenticated, project-scoped MCP surface that can start Config Registry analyses and influences browser/proxy setup before session creation; mitigated by validation and existing SDK contracts.

Overview
Adds a project-scoped MCP standalone tool resolve_browser_config so agents can query Config Registry before creating a browser.

The tool supports three actions: lookup (immediate cached browser/proxy recommendations), resolve (kick off a background analysis when cache is empty), and get_analysis (poll by analysis_id). Responses are passed through from the Kernel SDK without reshaping. Tool description documents the lookup → resolve → poll flow and that managed proxy recipes should be created via manage_proxies.

Wiring: new config_registry toolset in MCP registration, allowlist alias resolve_browser_config, entry in KERNEL_MCP_TOOL_NAMES, README standalone-tools list, and contract tests for registration allowlists and tool behavior.

^{Reviewed by Cursor Bugbot for commit b2be582. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

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

Project	Deployment	Actions	Updated
mcp	Ready	Preview	Sep 17, 2026 2:20am UTC

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8e6f40f. Configure here.}

[rgarcia]

reviewed — this looks superseded by #196, which already merged Config Registry support into main via manage_config_registry (including lookup, resolve, analysis polling/cancellation, listing, and structured 409 handling). this branch now conflicts with main and would introduce a second, narrower MCP surface for the same operations. i think we should close this PR unless there’s a specific UX change here that should be applied on top of #196.