⌘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
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Amy Egan Are you able to see your projects now?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
DkCorp hi, help plis.
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.
Nicosuaya 2179 I am seeing the same issue on a Pro team where the connected account is a confirmed Owner. Vercel Support directed me here. Read-only checks on October 12, 2026: - list_teams returns the correct team, and get_team succeeds. - list_projects without a team selector returns the existing team-owned project. - The returned project accountId and the team ID from list_teams are identical in a character-by-character comparison. - list_projects with that exact teamId returns an empty list. Using the verified slug also returns an empty list. - get_project for the existing project succeeds without an explicit team selector, but returns 404 with the correct teamId or slug. Before pausing writes, create_git_project with an explicit teamId and deploy:false returned 403, saying the account did not have permission to create the project. No project or deployment was created. Two OAuth reconnections did not resolve it. During the latest consent flow, the team row visibly showed Authorized before Allow Access was completed. The connection lists Projects Read/Write permissions. Could the Vercel MCP team clarify whether the Authorized badge can still coexist with a restricted project grant, what the team-row Configure control covers, and how an end user can inspect the effective project scope of an existing ChatGPT grant? Is there a supported fix for the different results with implicit versus explicit team scope? This is an MCP/API authorization issue, not a website-level 404. I am not trying to bypass the explicit scope or change production settings. Account details, repository names, team/project IDs, request IDs, source code, and credentials are omitted from this public reply. Please indicate a secure channel if identifiers are needed. Update: list_deployments, limited to one result for the same existing project, also succeeds without a team selector and returns 403 when the exact verified teamId is supplied. The asymmetry therefore affects both project and deployment reads.
Djm 1808 I’m experiencing the same issue through the Vercel app in ChatGPT Work. Read-only checks on **15 October 2026** show: - The connector identifies the correct Vercel account. - `list_teams` returns the correct team, and `get_team` succeeds. - `list_projects`, with the correct `teamId` explicitly supplied, returns `{"projects":[],"pagination":{"count":0}}`. - `get_project`, using `idOrName` with either the project ID or name and explicit team scope, returns **404 — Project not found**. - Looking up an existing deployment with explicit team scope also returns 404. The project is accessible through my Vercel dashboard. I disconnected and reconnected the app, completed OAuth consent, and checked the connection under “Sign in with Vercel”. Its listed permissions include projects, deployments and team data. Repeating the project-listing test in a fresh ChatGPT conversation still returns zero projects. The 404 occurs in the connector’s project lookup. This is blocking deployment work through ChatGPT. Could the Vercel MCP team investigate the effective team/project authorization and confirm the supported resolution? I can provide account, team, project and request IDs privately through a secure support channel.
