⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
yasoob Hi eric, thanks for letting us know. Could you please try again? The Prisma team has just pushed out a fix.
eric Hi yasoob, thanks for the follow-up, and sorry for the late reply. I just tested it again and the issue is resolved now. I do want to share some feedback, though. Because of this error, we had to remove the Prisma Postgres integration from our service and migrate to a different database provider. An issue like this takes the whole service down, not just one feature. It took a long time to get a response, and in the meantime there was nothing we could do on our end. No status update, no workaround, no escalation path. For integrations that sit on the critical path, like database auth/SSO, a faster response channel or at least visible incident status would make a big difference. Thanks again for looking into it.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Winwar94 Thank you for the troubleshooting guide. Our issue is not a website-level 404 or a missing deployment. The project exists, is accessible from the Vercel Dashboard, and has READY Preview deployments. Through ChatGPT Vercel MCP: * Project lookup without explicit teamId succeeds. * The same lookup with the owning teamId returns 404. * Deployment listing with explicit teamId returns 403. Other Community reports describe closely matching behavior, including: https://community.vercel.com/t/chatgpt-vercel-mcp-returns-empty-projects-and-404-with-explicit-team-scope/49644 https://community.vercel.com/t/vercel-mcp-in-chatgpt-empty-projects-and-403-despite-explicit-teamid/49520 Could the Vercel MCP engineering team investigate the effective OAuth team grant and explicit team-scope resolution? We can provide request IDs privately. No changes to Production are authorized. Thank you.
Winwar94 Thank you for the automated response. The generic “Debugging 404 Errors” guide does not appear to address our issue, since the staging project exists and its previous Preview deployments are accessible in the dashboard. We have confirmed the following behavior through ChatGPT’s Vercel MCP integration: * Project lookup without explicit teamId: HTTP 200. * Same project lookup with its correct teamId: HTTP 404. * Deployment listing with explicit projectId and teamId: HTTP 403. * Team-scoped project listing: staging project missing. * Authenticated user: confirmed Team Owner. We also found similar reports: https://community.vercel.com/t/vercel-mcp-in-chatgpt-empty-projects-and-403-despite-explicit-teamid/49520 https://community.vercel.com/t/chatgpt-vercel-mcp-returns-empty-projects-and-404-with-explicit-team-scope/49644 Could someone from the Vercel MCP engineering team investigate whether this is caused by OAuth team permissions, team scope propagation or API routing? We can provide request IDs through a private support channel. This is blocking a staging-only deployment needed to validate an operational bug fix. We have not attempted an unsafe deployment, and Production must remain unchanged. Thank you.
Ashokcchander 8888 Additional read-only diagnostics — October 10, 2026, approximately 4:50 PM Pacific / 23:50 UTC. We reproduced a difference based solely on whether an explicit team selector is supplied. Project: quintascent-picio-pilot-v1 Project ID: prj_HkwvurhrAMytl7Xb74iiDmCLAM4q Team slug: quitascent Team ID: team_IKgnMSNmT2TNQeoQoCmPyZ5b Results: 1. get_project({idOrName: "prj_HkwvurhrAMytl7Xb74iiDmCLAM4q"}) succeeds. Its response contains accountId: "team_IKgnMSNmT2TNQeoQoCmPyZ5b". 2. The identical lookup with teamId: "team_IKgnMSNmT2TNQeoQoCmPyZ5b" returns 403 Forbidden. 3. The identical lookup with slug: "quitascent" also returns 403 Forbidden. 4. list_deployments with the project ID and no explicit team selector succeeds; the latest two deployments report READY. 5. Earlier list_teams returned an empty list, and direct get_team returned 403. Both failed project lookups identify operation GET /v9/projects/{idOrName} and report: “Not authorized: Trying to access resource under scope "quitascent". You must re-authenticate to this scope or use a token with access to this scope.” Request IDs: - Explicit team ID: sfo1:sfo1::kzw9q-1791676217409-b1ae2808143c - Explicit slug: sfo1:sfo1::ltb42-1791676217674-f6e77d7f6a14 Error metadata: saml=false; ssoEnforced=false. The connector additionally labels the failure INVALID_ARGUMENT, while the underlying API error is 403 forbidden. The Vercel account UI shows quitascent as the default team. The ChatGPT application, owned by Vercel MCP, displays permission to read Vercel team data and read/change authorized projects. Could you trace these request IDs and check why implicit/default-team project access succeeds while explicitly selecting the same owning team fails? Is this expected authorization behavior, a missing team-specific grant, or a connector scope-resolution issue? These tests were read-only. No credentials, deployment protections, or project settings were changed.
Ashokcchander 8888 Additional comparison using Vercel Agent’s separate credentials: • Project lookup succeeds with both the owning team ID and slug “quitascent.” • Team listing includes quitascent, and direct team lookup succeeds. • The project’s accountId matches the supplied team ID. • Deployment listing succeeds. ChatGPT MCP still shows the contrasting behavior documented above: project access without an explicit team selector succeeds, but explicit team ID/slug access returns 403, and team listing is empty. Vercel Agent could not inspect ChatGPT’s effective OAuth grant or token context. Please check whether the ChatGPT connection has an effective grant for this specific team and whether explicit team selectors are resolved correctly. The displayed “read team data” permission alone does not settle that question. No settings or resources were changed in either diagnostic.
