This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
AI Agents Listing
The agentic AI ecosystem, in one directory
A directory of the agentic AI stack: AI agents that do real work, MCP servers that connect them to your tools and data, and agent skills that extend what they can do. Every listing gets an indexable page, and pages link across the three layers, so an agent shows the MCP servers it works with and the skills that extend it. Search, categories, comparisons and alternatives run across all of it. Listing is free.
Every agent directory ignores MCP servers. Every MCP registry ignores agents. Skills have no directory at all beyond GitHub readmes. If you are building with agents today you are searching three places that do not know about each other.
AI Agents Listing indexes all three layers in one place and links them to each other. An agent's page shows the MCP servers it works with and the skills that extend it. An MCP server's page shows the tools it exposes and the skills that use it. Search and categories run across all three, and every listing has its own indexable page with a description, pricing, setup and links.
A few things I decided on purpose:
Rankings are engagement, not money. Paid tiers get placement and a label. The trending lists never sort by what somebody paid, because a list you can buy into is the list nobody uses.
Agents can read it too. There is an MCP endpoint that answers what is trending and what works with what, no login needed, and an llms.txt for the rest.
Solo project. It started from the Dirstarter directory boilerplate (Next.js and Postgres) and grew the three-layer model and the cross-links on top of it. Self-hosted. I read every submission myself.
I would rather have your criticism than your upvote. The thing I am least sure about is whether cross-linking three layers reads as useful or as clutter on a listing page, so tell me which it was for you.
Thanks a lot
🔥❤️
About AI Agents Listing on Product Hunt
“The agentic AI ecosystem, in one directory”
AI Agents Listing was submitted on Product Hunt and earned 15 upvotes and 2 comments, placing #13 on the daily leaderboard. A directory of the agentic AI stack: AI agents that do real work, MCP servers that connect them to your tools and data, and agent skills that extend what they can do. Every listing gets an indexable page, and pages link across the three layers, so an agent shows the MCP servers it works with and the skills that extend it. Search, categories, comparisons and alternatives run across all of it. Listing is free.
On the analytics side, AI Agents Listing competes within Productivity, Developer Tools and Artificial Intelligence — topics that collectively have 1.7M followers on Product Hunt. The dashboard above tracks how AI Agents Listing performed against the three products that launched closest to it on the same day.
Who hunted AI Agents Listing?
AI Agents Listing was hunted by Nick Launches. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of AI Agents Listing including community comment highlights and product details, visit the product overview.
Nick Launches
Hi Product Hunt 🔥.
Every agent directory ignores MCP servers. Every MCP registry ignores agents. Skills have no directory at all beyond GitHub readmes. If you are building with agents today you are searching three places that do not know about each other.
AI Agents Listing indexes all three layers in one place and links them to each other. An agent's page shows the MCP servers it works with and the skills that extend it. An MCP server's page shows the tools it exposes and the skills that use it. Search and categories run across all three, and every listing has its own indexable page with a description, pricing, setup and links.
A few things I decided on purpose:
Rankings are engagement, not money. Paid tiers get placement and a label. The trending lists never sort by what somebody paid, because a list you can buy into is the list nobody uses.
Agents can read it too. There is an MCP endpoint that answers what is trending and what works with what, no login needed, and an llms.txt for the rest.
Solo project. It started from the Dirstarter directory boilerplate (Next.js and Postgres) and grew the three-layer model and the cross-links on top of it. Self-hosted. I read every submission myself.
I would rather have your criticism than your upvote. The thing I am least sure about is whether cross-linking three layers reads as useful or as clutter on a listing page, so tell me which it was for you.
Thanks a lot
🔥❤️