Where the Entries Come From
Agentwire is not a search over GitHub. Nothing arrives here because it matched a query or because it is large. An entry is in the index because other people had already affirmed it, and this page is where those people are — the lists, the threads and the metadata the lane actually reads.
The curated lists
A curated list is a repository whose whole content is somebody’s selection of other repositories, kept up by hand under their own name. It is the strongest signal the lane has, because a maintainer adding an entry puts their list’s reputation behind it, and no star count can fake a person choosing to vouch.
These are the lists the entries in the index cite. They are other people’s work, they are worth reading directly, and each one is linked here for that reason:
punkpeye/awesome-mcp-servers — carries mcp by awslabs, whatsapp-mcp by lharries, terraform-mcp-server by hashicorp, GhidrAssistMCP by symgraph, hindsight by vectorize-io, Unity-MCP by IvanMurzak, blender-mcp by ahujasid, wigolo by KnockOutEZ, exa-mcp-server by exa-labs, codebase-memory-mcp by DeusData and magic-mcp by 21st-dev.
kyrolabs/awesome-langchain — carries XAgent by OpenBMB, gpt-researcher by assafelovic, SuperAGI by TransformerOptimus, CopilotKit by CopilotKit, haystack by deepset-ai, codeinterpreter-api by shroominic, codel by semanser and DemoGPT by melih-unsal.
wong2/awesome-mcp-servers — carries mcp by awslabs, mcp by hyperbrowserai, mcp-server by mapbox, skyvern by Skyvern-AI, exa-mcp-server by exa-labs and magic-mcp by 21st-dev.
e2b-dev/awesome-ai-agents — carries XAgent by OpenBMB, gpt-researcher by assafelovic, agents by aiwaves-cn and DemoGPT by melih-unsal.
Hacker News
A thread above forty points pointing at a repository is a room full of developers who had the same question and stayed to argue about the answer. The lane reads the thread, not the vote count on its own — the points are only the bar a thread has to clear before it counts as anything.
In the index on this signal: mcp-agent by lastmile-ai, whatsapp-mcp by lharries, terraform-mcp-server by hashicorp, mcp by hyperbrowserai, crush by charmbracelet, mcp-server by mapbox, GhidrAssistMCP by symgraph, blender-mcp by ahujasid and skyvern by Skyvern-AI. All of them.
GitHub’s own topic metadata
Repository owners tag their own work with topics — mcp, agent, llm-agent and the rest. The lane reads those topics because they are the owner’s own statement of what a thing is, which is the one description of a project nobody here has to write. A repository carrying two or more agentic topics counts as one signal, and only one: a tag is a claim about category, never about quality, and an honest tag on the wrong kind of tool still gets that tool left out.
Why not just search GitHub
You can, and for a lot of questions you should — every entry here links straight back to the repository, and GitHub is where the code, the issues and the actual maintainers are. What a search returns is everything that matched, ordered by size, including the large number of things nobody has ever vouched for. That ordering answers “what is popular”, which is a different question from “what did somebody stake their name on”.
The lists above are where the second question already gets answered, by people who do it for their own reasons and maintain it by hand. Agentwire reads several of them at once and requires two independent signals before anything ships, so a coincidence on any one of them does not make it in. That is the whole of the addition. It is a narrower net than a search, on purpose.
Which list you read changes what you are shown, because each one has a different rule about who may add an entry — and on most of them the answer is the author of the tool. Where MCP servers get listed in 2026 sets out each listing’s submission policy in its maintainers’ own words, this index included, and ranks none of them.
What this page is not
It is not a ranking of the lists, and nothing here says one is better kept than another. Agentwire does not test what it shares and has not audited anybody’s list — it records which ones an entry appeared on, because that is the evidence the entry is here at all. How eligibility is decided says the rest, including where the ceiling is and what gets left out.
If you maintain a list named here and would rather not be, or an entry cites you wrongly, say so at hello@kynth.studio and it comes off.