Launched this week
Remote OpenClaw
13,000+ MCP servers, skills & plugins for AI coding agents
85 followers
13,000+ MCP servers, skills & plugins for AI coding agents
85 followers
Remote OpenClaw is the largest open directory of building blocks for AI coding agents: 13,000+ MCP servers, agent skills, plugins, and ready-made workflows for Claude Code, Codex, OpenClaw, and Hermes. Stop hunting across GitHub, npm, and scattered docs. Find, compare, and install everything in one place. Filter by client, category, and use case, copy the install command, and go. Free to browse, no login required.
Installing cleanly is table stakes, but the thing that actually made me drop servers was the cost of just having them connected. One I tried registered 41 tools and ate roughly 12k tokens of context before the agent did anything, and with three servers attached it started picking the wrong tool because the list got too long to reason over. Does the directory expose tool count and total schema size per server? That is the number I would sort by.
@dipankar_sarkar Really sharp point, and it's a failure mode most people don't notice until an agent starts mis-selecting tools. Context cost is a real quality signal: 41 tools and 12k tokens before you've done anything is a tax on every run. We don't surface tool count or total schema size per server yet, but you've convinced me it belongs on the listing, and it's exactly the kind of thing you'd want to sort by. Adding it. Thanks for the concrete example.
Would love to see a "compatibility check" feature that warns you if an MCP server or skill hasn't been updated for your specific client version before you copy the install command, saves people from troubleshooting broken installs later.
@kadervm1i Love this. A "this hasn't been updated for your client version" warning before you copy the command is exactly the kind of thing that saves an hour of troubleshooting. It fits right into the reliability layer we're building: catch the broken install before it happens instead of after. Noting it down.
Honestly love that you can just copy the install command straight from the listing, no extra clicks or digging through docs. Filtering by client and use case upfront is the kind of thing that sounds small but saves a ton of time when you're setting up a new agent.
@sabrihakverdi Thank you, killing that friction was the whole point. Copying the install command straight from the listing and filtering by client up front sounds small but it's the difference between five minutes and an afternoon. Really glad it landed.
Love that this exists, the copy-paste install flow is exactly what I needed today. One thing that would make it even better: a community upvote or "works on" badge so I can quickly tell which MCP servers are actually maintained and battle tested versus abandoned. Right now everything looks equal at a glance.
@nebahatkormazer Appreciate it. You're spot on that everything looks equal at a glance right now, and that's the main thing I want to fix. A "works on" / maintained badge so you can instantly tell battle-tested from abandoned is high on the list. A few people here asked for the same thing, so it's clearly the gap.
Love having everything in one spot, the copy-paste install command alone saves me a ton of clicks. One thing that would be huge: a "last verified working" date or health badge per listing, since MCP servers go stale fast and I'd rather know before wiring one into a project.
@mehmet_ayd30839 Thank you. And yes, a "last verified working" date is exactly the signal we're building toward. MCP servers go stale fast and stars don't tell you if it still boots today. That plus install success is the reliability layer coming next. You and a couple of others all landed on the same need, which tells me it's the right thing to build.
Love that the install commands are right there alongside the filters, no extra clicks needed. The directory feels fast and clean too, not like the usual bloated registry pages.
@aynurkrbykyt2b Thank you, the "not bloated" part means a lot. So many registries turn into heavy pages that make you work to find anything, so keeping it fast and letting you copy the install command without hunting was the whole goal. Glad it feels that way.