landscape · Julien de Waal · 9/7/2026 · 6 min read
AI Agents Listing Is the First Directory to Index Agents, MCP Servers, and Agent Skills Together
The agentic stack has a discovery problem
If you've spent time assembling an agent stack in the last twelve months, you know the drill. You're searching across GitHub repos, Discord servers, and half a dozen fragmented directories just to answer one question: what tools actually exist for this layer of the stack?
AI agents live in one index. MCP servers live in another. Agent skills — the reusable capability modules that sit between them — often don't have a home at all. You're not missing something. The infrastructure genuinely didn't exist.
That's the gap AI Agents Listing was built to close.
What AI Agents Listing actually indexes
Launched by a solo founder named Nick, AI Agents Listing is a bootstrapped, self-hosted directory that models the agentic stack as three distinct but connected layers:
- AI agents — autonomous systems that plan, reason, and execute tasks
- MCP servers — the Model Context Protocol infrastructure that lets agents communicate with tools and data sources
- Agent skills — discrete, reusable capabilities that can be composed across agents
The project's core premise is simple but underserved: these three layers belong in one index because they don't function in isolation. An agent without skills is a shell. A skill without an MCP server has no delivery mechanism. Searching across three sites that don't reference each other wastes the time of every founder trying to build.
"I built this because I was searching three sites that did not know about each other," Nick said at launch.
That's a product brief written in one sentence.
Why the three-layer model matters now
The Model Context Protocol (MCP), introduced by Anthropic in late 2023 and rapidly adopted across the ecosystem, gave agent developers a standardized way to connect language models to external tools and data. It changed the architecture of agent systems from bespoke integrations to something closer to modular infrastructure.
The consequence: the number of MCP servers, agent frameworks, and reusable skill packages grew fast — and outpaced any existing discovery layer. Smithery, Glama, and a handful of GitHub lists index parts of this. None index all three layers in relation to each other.
AI Agents Listing is a direct response to that fragmentation. The three-layer framing isn't marketing — it reflects how production agent stacks are actually built. You pick your agent framework, wire it to MCP servers for tool access, and compose skills to handle specific subtasks. Discovering those components should happen in one place.
The solo founder signal
What makes this launch worth watching beyond the product itself is the model behind it. Nick built and shipped a self-hosted directory that addresses a real coordination failure in a fast-moving ecosystem — alone, bootstrapped, with no funding announcement.
That's consistent with a pattern showing up across the AI-native companies landscape in 2026: the highest-leverage early moves in infrastructure are increasingly made by solo builders who identify friction before larger teams do, ship fast, and iterate in public.
The economics follow the same logic that makes revenue per employee the defining metric of this era. A directory built and maintained by one person, running on self-hosted infrastructure, doesn't need a Series A to reach meaningful scale. The marginal cost of indexing another agent or MCP server is close to zero. The value compounds with each listing.
This is the one-person-unicorn model applied to infrastructure: find a gap, build the minimum structure that closes it, own the category before anyone else realizes the category exists.
What's currently indexed — and what's missing
At launch, AI Agents Listing covers the major agent frameworks (AutoGen, CrewAI, LangGraph, and others), a growing index of MCP servers, and an emerging catalog of agent skills. The directory is open for submissions, which means the index quality will reflect how quickly the builder community engages.
The honest limitations: early-stage directories live or die on curation quality. A comprehensive index of every MCP server ever pushed to GitHub isn't useful if half are abandoned proofs of concept from November 2023. The value Nick is building toward is a curated, maintained, cross-referenced index — not just a list. How that curation scales as the ecosystem grows will determine whether AI Agents Listing becomes the definitive resource or a useful snapshot.
For now, it's already the most complete single-layer view of how the agentic stack fits together that exists publicly.
How to use it as a builder
If you're assembling an agent stack — for a product, for internal automation, or for a client — the practical workflow is straightforward:
1. Start with the use case. What does the agent need to do? That defines which skills you need. 2. Find the skills first. If a reusable skill module exists, you don't build it. 3. Match to an MCP server. Identify what tool access and data context your agent needs, then find the server that provides it. 4. Pick your agent framework last. The framework should fit the architecture, not drive it.
AI Agents Listing makes step two and three faster. That matters because the bottleneck in agent development right now isn't the LLM — it's discovery and integration time.
Julien de Waal, who spent 16 years managing growth, product, and marketing teams across crypto, fintech, and SaaS before building the AI-native systems that replaced those departments, has made a similar point about stack assembly: the constraint isn't capability, it's knowing what already exists well enough to stop rebuilding it. Directories like AI Agents Listing reduce that rebuild tax.
The directory as an asset class
There's a broader point here about directories as a business model for solo founders. A well-maintained, category-defining directory in a fast-growing space attracts organic search traffic, builds community, and creates a distribution channel — all without a sales team.
The model isn't new. What's new is the speed at which an agentic AI directory can reach authority. The ecosystem is twelve to eighteen months old. Categories are forming in real time. A solo founder who indexes the right layer of the stack before the category consolidates owns a compounding asset.
For founders building a one-person startup with AI, that's the playbook worth studying here — not just the product, but the timing and the structural bet.
AI Agents Listing is live. Submissions are open. The index is being built in public.
Whether it becomes the canonical directory for the agentic stack depends on execution from here — but the category it's targeting is real, the problem it solves is real, and the solo founder behind it shipped it before anyone else did.
That's usually how these things start.
---
Is your company eligible? Submit to the leaderboard → onepersonunicorn.co/submit
Read the full AI-native companies guide.
Is your company eligible? Submit to the leaderboard →
Submit Your Company