Pauline P. Narvas Hey, Nico! Can you check the following? **File Structure** * Is your file structure exactly as follows? ``` app/ ├── mcp/ │ └── route.ts └── internal-api/ └── mcp/ └── route.ts ``` * Is the `/internal-api/mcp/route.ts` file located exactly where you think it is? --- **Middleware Matcher** * Does your middleware matcher correctly exclude the intended directories? ``` matcher: ["/((?!api|_next|internal-api|mcp|.*\\..*).*)"] ``` * Could the matcher still be interfering with the route in unexpected ways? --- **Route Handler Export** * In `/internal-api/mcp/route.ts`, are you exporting your handlers like this? ```ts export { handler as GET, handler as POST, handler as DELETE }; ``` * Are the imports and export names correct and consistent? --- **Debugging Steps** * Does the route work when you visit it directly in the browser? * Is the file definitely located at `app/internal-api/mcp/route.ts`? * Does a minimal test handler work? ```ts export async function GET() { return Response.json({ message: "Internal MCP route working" }); } ``` * Do you see any relevant console or server logs when you hit the route? --- **BasePath Configuration** * Are you using `basePath: ""` in both handlers? * Could the shared or empty `basePath` be causing conflicts? * Does the issue go away if you remove or change the `basePath`?
Nico Laeser Hi, Seems like the baseUrl was the Problem! Fixxed it now!
Kapehe These open source builders are out here changing the web! We’re honored to be able to support them! 🙇🏻♀️
Avik Creator And I am grateful that vercel exists. Btw I am preparing my project for next Vercel oss. https://formcraftai.avikmukherjee.me Would really love your feedback on this, if possible. Thank you
Pauline P. Narvas Great questions! Good luck getting contributions to this, I hope that folks in our community share some answers. Have you seen @eric-burel's work? He's done a lot of similar community work! We also did this session with him a couple of weeks back which may be helpful for your questionnaire and research. https://community.vercel.com/t/community-session-vercel-for-smes-and-open-source/9071
DRO Thanks for the tip Pauline! I will check it out. Note for others: submissions are closed as the deadline for delivery has been reached. I will mark this topic hopefully in such a way that this is clear.
Dominik Koch Meet Brandon a bit ago in SF, hes been cooking with toolwind. I really love what you did here Brandon!
Pauline P. Narvas This looks like a great initiative for the Tailwind CSS community! Toolwind sounds like it could be a valuable resource for developers looking to discover and evaluate Tailwind plugins more efficiently. Nice badge, btw!
Pauline P. Narvas Hey Dorian! 🎉 Huge congrats on being accepted into the Vercel OSS Program 2025 Spring Cohort. That’s *amazing*! It’s been so cool to see Kokonut UI grow from a personal project into something that’s genuinely supporting the broader Next.js and React community. The integrations with both the shadcn/ui CLI and v0 sound incredibly useful, especially for folks who want to prototype and customize components quickly. And honestly, being one of the first to figure out the shadcn CLI integration *without* any docs? That’s some serious dedication. 👏 Thank you for sharing this with the community and for everything you’re contributing to open source. Can’t wait to see where you take Kokonut UI next! 💜
Dominik Koch Oh wow these components look amazing. I think the Apple Activity Card is my favorite. Any chance you could make a gauge version of that? Something like this would be sick:
David Moreno Thanks for sharing, Christian! This looks super helpful — I appreciate your work on making i18n management easier in Next.js projects. 🙌
Christian Ivicevic Thanks for the kind words - let me know if you were able to give it a try and whether everything works as expected. After all, it's quite the difference running this "just" for my own side projects and having others attempt to integrate it into their own workflows.