⌘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
Knowledge1010 Confirming the get_project parameter mismatch from a separate account on September 22, 2026, using the installed Vercel connector in the Codex desktop app on Windows. Vercel support directed this report here because MCP is in Beta. In this test, list_teams, list_projects, and list_deployments all succeeded. I did not reproduce the empty-project list or 403 errors in the original post; the shared defect is specifically get_project. Reproduction: 1. Obtain valid project and team IDs from the successful list calls. 2. Call get_project with the advertised fields: {"projectId":"VALID_PROJECT_ID","teamId":"VALID_TEAM_ID"}. These strings are placeholders here; actual valid IDs were used in the test. 3. The response is: "Input validation error: Invalid arguments for tool get_project: idOrName: Invalid input: expected string, received undefined" (isError=true). 4. Retrying with an additional idOrName field alongside projectId and teamId produced the same error. Whether the client adapter drops the unadvertised field has not been established. Expected: the advertised input schema should return project details. The public MCP tool reference also documents projectId and teamId: https://vercel.com/docs/agent-resources/vercel-mcp/tools Impact: individual project details are unavailable through this connector, while project/deployment listing works. This is not a production outage or a general authentication failure. Please route this to the MCP/connector integration team to align the exposed schema with the handler, map projectId to idOrName if required, and add a contract test using the advertised arguments. Please also confirm whether the mismatch is in Vercel MCP or the Codex connector adapter. No credentials, account/project IDs, or customer data are included in this public report.
Thomas Thank you for independently reproducing the get_project mismatch and for distinguishing it from the other symptoms. A fresh read-only test of my connection on September 22 still shows: list_teams succeeds. list_projects returns an empty list with the correct team ID explicitly included. list_deployments returns 403 Forbidden with both the recorded project ID and team ID explicitly included. get_project returns the same missing-idOrName validation error. Your report corroborates the project-lookup mismatch across accounts. My project-listing and deployment-access failures remain an additional unresolved issue; I am not assuming they share the same cause. Could a maintainer confirm which team owns the schema/handler mismatch and whether a fix is being tracked? Please also advise whether the listing/access failures should be investigated in a separate thread and what sanitized diagnostic information would help. I can provide account identifiers through an appropriate private support channel.
National Scouting Combine Hello Vercel MCP team, Vercel Support directed me to the Community because MCP is a Beta feature. I am adding another reproduction involving the connected Vercel app in ChatGPT and our NSC Network project. I have already disconnected and reconnected the integration. Read-only checks continued to fail in a subsequent conversation. Latest checks — October 3, 2026 1. Team-scoped project listing returns 403 Calling list_projects with our actual team ID explicitly supplied returns the following error. The team slug is redacted here: 403 Forbidden Not authorized: Trying to access resource under scope "[TEAM_SLUG]". You must re-authenticate to this scope or use a token with access to this scope. The response identifies the expected team ID. Retrying with the team slug during the earlier audit also returned 403. 2. The exposed get_project schema does not match validation The connected tool requires: { "projectId": "[ACTUAL_PROJECT_ID]", "teamId": "[ACTUAL_TEAM_ID]" } Actual resource IDs—not these placeholders—were supplied. The response is: Input validation error: Invalid arguments for tool get_project: idOrName: Invalid input: expected string, received undefined The current Vercel MCP documentation lists idOrName as required, but the connected tool exposed to ChatGPT still requires projectId. Please investigate whether the mismatch is in the MCP server, the published integration schema, or the connector adapter. Documentation checked: https://vercel.com/docs/agent-resources/vercel-mcp/tools/projects/get_project Additional results from the earlier read-only audit Check Result list_teams Empty teams array; count zero get_deployment with explicit team ID Team-scope 403 web_fetch_vercel_url for our beta site 403 at stage: "read_protection_bypass" The URL-fetch error referenced our expected deployment, but did not return application content. These results do not establish that the website is down or that DNS is misconfigured. Requested investigation Please investigate the effective account identity and team authorization associated with the existing connection, and separately investigate the projectId/idOrName mismatch. Please confirm whether these symptoms are linked to an existing tracked issue, and identify the next diagnostic step beyond repeating disconnect/reconnect. A secure channel for providing team, project, and deployment identifiers would also help. Impact: The connection cannot reliably inspect our project or deployment, blocking the deployment audit through ChatGPT. No deployments, permission changes, protection changes, or DNS changes were made during these checks. We are requesting diagnosis, not a workaround that weakens security. Thank you.
Amy Egan Hey @hectorbernstorff. If you let me know the case number, I can look into it for you
Ronnie Sasmay a mi me pasa algo similar y aun no me respomden dice 3 semanas ya va casi un mes se cambia automaticamente a un modelo pro y sin consentimiento ni aviso sin darme cuanta ya he consumido todos los creditos, una estafa,m ellos dicen que funciona asi.
Hectorbernstorff Hi Amy — thank you, and sorry for the delay. The case numbers: - 01vtjq9Y6UhJT3V5 (invoices K1C0Q027-0018, -0019 and -0020 plus residual fees, $902.53): opened Sep 8, three follow-ups, still no human reply. - 01CIQPqjyMcK7UIq (August invoice K1C0Q027-0021, $387.01 asked): a $100 one-time goodwill was granted on Sep 28, and the case was auto-closed on Oct 1 before the second-level review I requested was answered. A look at either one — or a written no with the policy clause being applied — would let me close this cleanly. Team: hector-mercedes-projects. Thank you!
Jsjshsh775 4873 This is what I say too
Amy Egan Thanks for sharing your feedback! The referral program was removed for many reasons, and there are no immediate plans to bring it back But everyone should feel free to keep adding comments here to let us know what the referral program meant to you and your ideas about how Vercel can support new devs on v0 in the future. I'll share them with the team
