config: add ai-gateways, llm-gateways, mcp-gateways

[GeniusTechnoMystic]

What problem does this PR solve?

Issue Number: N/A

Problem Summary: This PR adds new AI Gateway-related collections to OSS Insight, allowing users to explore and analyze repositories in the AI Gateway ecosystem.

What is changed and how it works?

This PR adds the following collection configuration files under configs/collections/:

• 10104.ai-gateways.yml - A collection of AI Gateway repositories
• 10105.llm-gateways.yml - A collection of LLM Gateway repositories
• 10106.mcp-gateways.yml - A collection of MCP Gateway repositories

Each collection file follows the standard format with:

• Collection ID (100XX format, incrementing)
• Collection name
• List of relevant GitHub repositories

Users will now be able to view and analyze these collections on the OSS Insight website.

These collections were generated from the following gh searches:

gh search repos --topic ai-gateway
gh search repos --topic llm-gateway
gh search repos --topic mcp-gateway

The ai-gateways collection is the union of all 3 sets.

[GeniusTechnoMystic]

I update the 3 collections based on the following repo search results:

gh api --paginate -X GET /search/repositories -F per_page=100 -f q="llm-gateway OR llm-proxy OR llm-router OR model-gateway OR model-proxy OR model-router" -f sort=stars -f order=desc --jq '.items[] | "[(.stargazers_count)★ | (.forks_count)⑂ | (.open_issues_count) issues] (.full_name): (.html_url) (Active: (.pushed_at))"' > llm-gateways-list.txt

gh api --paginate -X GET /search/repositories -F per_page=100 -f q="ai-gateway OR ai-proxy OR ai-router" -f sort=stars -f order=desc --jq '.items[] | "[(.stargazers_count)★ | (.forks_count)⑂ | (.open_issues_count) issues] (.full_name): (.html_url) (Active: (.pushed_at))"' > ai-gateways-list.txt

gh api --paginate -X GET /search/repositories -F per_page=100 -f q="mcp-gateway OR mcp-proxy OR mcp-router" -f sort=stars -f order=desc --jq '.items[] | "[(.stargazers_count)★ | (.forks_count)⑂ | (.open_issues_count) issues] (.full_name): (.html_url) (Active: (.pushed_at))"' > mcp-gateways-list.txt

[sykp241095]

Hi @GeniusTechnoMystic, thanks for putting this together! 🙌

We took a look at the three proposed collections and noticed a couple of things:

1. Significant overlap — many repos (Kong, litellm, Portkey, etc.) appear in all three collections. It might work better as a single unified "AI Gateway" collection.

2. Relevance — with 1000+ repos per collection, quite a few seem unrelated to the gateway/proxy theme (e.g. crawlee, casdoor, china-dictatorship). A tighter, curated list would be much more useful for users.

3. Size — our other collections typically have 5–50 repos. 1000+ makes the rankings less meaningful.

Would you be open to consolidating this into one collection with the top ~30-50 most relevant AI/LLM/MCP gateway projects? We can help with the curation if you'd like — just let us know!

[GeniusTechnoMystic]

OK, I'll see what I can do. Feel free to go ahead and do it if I don't get to it first.

[sykp241095]

Cleanup Done ✅

This PR has been superseded by #2283 which addresses the quality issues:

Problems found:

1. 10104.ai-gateways.yml had 1035 repos, the vast majority unrelated to AI gateways (random repos matched by keyword search)
2. 10105.llm-gateways.yml — ID 10105 already exists as mcp-servers.yml on main branch (conflict!)
3. 10106.mcp-gateways.yml — ID 10106 already exists as coding-agents.yml on main branch (conflict!)
4. IDs 10105 and 10106 also semantically overlap with existing collections: 10099.mcp-client.yml, 10105.mcp-servers.yml, 10115.llm-gateway-proxy.yml

What was done in #2283:

• Trimmed 10104.ai-gateways.yml to 13 carefully selected, high-quality AI gateway projects (all 500+ stars)
• Deleted 10105.llm-gateways.yml and 10106.mcp-gateways.yml to avoid conflicts

Please close this PR in favor of #2283.