[codex] Add MCP project management tool

[IlyaasK]

Summary

• Add manage_projects for Kernel project create/list/get/update/delete workflows.
• Register the projects tool through the new MCP capability module stack from PR 1.5.
• Keep project handling isolated in src/lib/mcp/tools/projects.ts so route.ts stays HTTP/auth-only.

Validation

• git diff --check codex/route-tools-breakdown...HEAD
• KERNEL_CLI_PROD_CLIENT_ID=dummy-prod KERNEL_CLI_STAGING_CLIENT_ID=dummy-staging KERNEL_CLI_DEV_CLIENT_ID=dummy-dev NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_Y2xlcmsuZXhhbXBsZS5jb20k bun run build
• python3 /Users/ilyaas/.codex/skills/autoreview/scripts/autoreview --mode branch --base codex/route-tools-breakdown
• localhost MCP CRUD smoke against http://127.0.0.1:3002/mcp with API_BASE_URL=http://127.0.0.1:3001: initialized MCP, verified manage_projects was listed, created a scratch project, got/updated/listed/deleted it, and confirmed post-delete get failed as expected

---

Note

Medium Risk
Introduces MCP-driven project update and delete against org resources; behavior is gated on existing MCP auth but mistaken agent use could archive or remove projects.

Overview
This PR exposes organization project lifecycle to MCP clients via a new manage_projects tool, wired through registerProjectCapabilities in the MCP capability registration path.

The tool supports create, list (with optional name filter and pagination), get, update (name and/or active/archived status), and delete, using the caller’s auth token and the existing Kernel client. Required fields are validated in-tool before API calls; failures return text errors rather than throwing to the host.

Project logic lives in src/lib/mcp/tools/projects.ts, consistent with other capability modules, so routing stays thin.

^{Reviewed by Cursor Bugbot for commit d92b043. 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, Comment	May 29, 2026 7:04pm

[firetiger-agent]

Monitoring Plan: MCP Server Tool Registration Refactored into Modules

What this PR does: Reorganizes internal MCP server code — moves tool, resource, and prompt registration from a single large file into separate module files. No tools added or removed, no user-visible behavior change intended.

Intended effect:

• Railway HTTP 5xx rate: baseline 0.0017–0.0039% (~4–9 errors/hr); confirmed if rate stays below 0.01% post-deploy
• MCP transport endpoint availability: baseline — low but steady traffic on MCP paths; confirmed if any MCP calls continue to return expected 200/401 responses (no new 500s)

Risks:

• Module initialization failure — if any registerX() call throws at startup, all MCP requests return 500; alert if Railway 5xx rate exceeds 0.01% for 30+ minutes post-deploy
• Profiles resource removal — profiles:// MCP resource was present in the old code but is absent from the new resources.ts; alert if any "resource not found" errors appear for profile URI lookups
• Import alias failure — @/lib/mcp/... path aliases must resolve at Next.js build/runtime; alert if any 500s appear immediately after deploy with module-not-found errors in logs
• Specific tool regression — any of the 11 newly-modularized tool files could have a subtle handler difference; alert if Railway 5xx rate on MCP paths rises above zero from baseline

Status updates will be posted automatically on this PR as monitoring progresses.

View monitor