Alternatives
Products that do what MCP2Skill does
Convert MCP tools into Skills that load on demand
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21AM
Hey HN! One of the biggest limitations of tools like Cursor is that they only have context over the project you have open. We built this MCP to allow you to fetch code context from all of your repos. It uses Sourcebot under the hood, an open source code search tool that supports indexing thousands of repos from multiple platforms. The MCP server leverages Sourcebot's index to rapidly fetch relevant code snippets and inject it into your agents context. Some use cases this unlocks include: - Finding all references of an API across your companies repos to allow the agent to provide accurate…
2025 · github.com
- 22LF
We built a no/low-code tool that lets you spin up MCPs from a single prompt. MCPs give LLMs access to tools, data, and actions—but they’re hard to build and deploy. Our tool abstracts that: describe what you want, and it auto-generates and hosts the necessary components. No UI flows, no manual chaining—just prompt and go. Examples: • Pull email, parse a DocSend, check Reddit, draft reply • Extract data from a niche site + send a Slack alert • Combine tools without writing glue code Live demo: https://www.youtube.com/watch?v=4uCiaQrgfoE Built over a weekend after getting…
2025 · generatemcp.com
- 23CA
Hi HN — I'm the creator of FastMCP and wanted to share a new project we've open-sourced called Colin. I obviously love MCP, but I also use skills extremely heavily in my day-to-day work. Being exposed to both has made me very aware of a tension: - Anything with dynamic information, I ship over MCP. This takes work to set up and requires conversational boilerplate to refresh in every conversation. - Anything behavioral, I put in skills. They're lightweight, used automatically, and feel great. But I would never put dynamic information in a skill because keeping it up to date is a pain. And yet…
Jan 2026 · github.com
- 24MM
I built MCPlexor to solve a token waste problem I kept running into with MCP-based agents. The Problem: MCP (Model Context Protocol) is great for giving LLMs access to external tools. But if you connect multiple servers (GitHub, Linear, Postgres, Slack), you end up with 40-50k tokens of tool definitions injected into every request – before the agent even does anything. On a 200k context model, that's 25% gone. On smaller models, it's worse. And most runs only use 1-2 tools. The Solution: MCPlexor sits between your agent and your MCP servers. Instead of loading all tool definitions upfront:…
Feb 2026 · mcplexor.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →