Keep MCP project selection optional

[rgarcia]

Summary

• allow organization-wide MCP connections to omit project_id
• preserve unscoped API behavior for cross-project reads and default-project creates
• keep project-scoped connections locked to their fixed project
• update connection guidance and regression coverage

Tests

• bun test
• bunx tsc --noEmit
• bun run check:managed-auth-app
• targeted Prettier check for changed files

bun run format:check continues to report the pre-existing formatting issue in AGENTS.md.

---

Note

Medium Risk
Changes how org-wide connections scope Kernel API calls (undefined vs forced project), which can alter list/create behavior for agents that relied on the previous required project_id error.

Overview
Organization-wide MCP connections no longer require project_id on project-scoped tools. Omitting it forwards undefined to the Kernel client so reads can stay org-wide and creates follow the API’s default-project behavior; passing project_id still selects a project explicitly.

get_connection_context now always reports project_id_required: false and its description/README guidance reflect optional selection on org-wide connections. Project-scoped connections are unchanged—they still resolve to the fixed project and reject mismatched overrides.

Tests cover unscoped org-wide calls (e.g. manage_auth_connections list without project_id).

^{Reviewed by Cursor Bugbot for commit e7d9477. 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 (UTC)
mcp	Ready	Preview	Aug 10, 2026 1:13pm