Community tool: searchable, agent-friendly Vercel Templates discovery — feedback wanted

Showcase
1

Hi Vercel team and community,

I built a small open-source tool that makes the Vercel Templates gallery searchable, comparable, and discoverable from agents and the terminal. I wanted to share it here and ask for feedback, especially from the Vercel team, on whether something like this could be useful officially or whether a public Templates API might be on the roadmap.

Project: imKXNNY/vercel-templates-discovery

What it does
Because there is no public Vercel Templates API (for discovery - i’m aware there are setup/install/create cli commands like create-next-app for most- to all templates) today, the tool indexes the gallery into a local SQLite database. It exposes:

  • Keyword search, semantic search (local embeddings via Ollama), recommendations, and template comparisons.
  • A CLI in both Python (pip install vercel-templates-discovery) and Node (npm install -g @imkxnny/vercel-templates-discovery).
  • A FastAPI REST server and a stdio MCP server, so agents like Claude Code, Cursor, Copilot, Codex, and Hermes can discover templates conversationally.
  • A cross-agent skill published on skills.sh.

The catalog can be rebuilt in under a minute, and a nightly GitHub Actions workflow keeps it fresh.

Why I built it
Vercel Templates is one of the best entry points for developers starting new projects, but there is no programmable way to search or recommend from it. As agents become a common first interface to tooling, I wanted to make the gallery discoverable inside those workflows without every project reimplementing the scraping logic.

Relationship to Vercel
This is currently an unofficial, community-maintained project. It is not affiliated with, endorsed by, or sponsored by Vercel. I’m happy to keep it that way, but I wanted to reach out in case it overlaps with Vercel’s plans or could meet your quality standards for a community tool.

Questions for the Vercel team

  1. Is a public Vercel Templates API on the roadmap? If so, I’d be happy to migrate the tooling to it.
  2. Would Vercel consider linking to or endorsing a community tool like this if it meets your security and quality standards?
  3. Are there guidelines or a preferred path for community tools that extend the Vercel developer experience?

Any feedback on the implementation, disclaimers, or branding is also very welcome. I want to make sure this is presented in a way that respects Vercel’s trademarks and terms of service.

Thanks for taking a look!

  • Kenny
1 Like