Alternatives
Products that do what Conduit does
Fix the tool-list bloat slowing your AI agent
- 1
- 2
- 3
- 4
13,000+ MCP servers, skills & plugins for AI coding agents
Jul 2026 · codexmarketplaces.com
- 5
- 6
- 7
- 8CS
Hi HN! Token cost has started to become a high topic of concern to all of us. I tried a few (awesome) tools such as rtk, caveman, and the recent (hillarious but effective) ponytail. What they usually do, is in-line token reduction, e.g. try to compress requests / responses as much as possible. But then it hit me (and I’m sure others had similar ideas) - just like we have routers that pick the right model, why not have something that will also narrow down the amount of available tools, skills and mcps based on repo/context? People usually accumulate skills, agents, MCP servers,…
Jun 2026 · github.com
- 9
- 10MM
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
- 11
- 12UM
Hey HN Community, I built MCP360 after spending weeks integrating APIs for an AI agent project. Each tool needed its own setup, auth, billing, and maintenance. When any APIs changed, my integrations broke. I got tired of it. MCP360 is a single gateway giving AI agents access to 100+ tools through one config block. Search engines, web scraping, SEO, e-commerce data, maps, domain tools, and more. Real example: Instead of managing Google Search, web scraping, SERP tracking, and keyword research as 4 separate subscriptions (4 bills, 4 auth systems, 4 points of failure), you connect once. Works…
Oct 2025 · mcp360.ai
- 13LC
Hi HN, I'm building Librarian (https://uselibrarian.dev/), an open-source (MIT) context management tool that stops AI agents from burning tokens by blindly re-reading their entire conversation history on every turn. The Problem: If you're building agentic loops in frameworks like LangGraph or OpenClaw, you hit two walls fast: Financial Cost: Token usage scales quadratically over long conversations. Passing the whole history every time gets incredibly expensive. Context Rot: As the context window fills up, the LLM suffers from the "Lost in the Middle" effect. Response latency…
Feb 2026 · uselibrarian.dev
- 14
- 15AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 16MS
As a consultant I foot my own Cursor bills, and last month was $1,263. Opus is too good not to use, but there's no way to cap spending per session. After blowing through my Ultra limit, I realized how token-hungry Cursor + Opus really is. It spins up sub-agents, balloons the context window, and suddenly, a task I expected to cost $2 comes back at $8. My bill kept going up, but was I really going to switch to a worse model? No. So I built l6e: an MCP server that gives your agent the ability to budget. It works with Cursor, Claude Code, Windsurf, Openclaw, and every MCP-compatible application.…
Apr 2026 · l6e.ai
- 17PR
Hi HN, While building RAG agents, I noticed a lot of token budget was wasted on formatting overhead (HTML tags, JSON structure, whitespace). Existing solutions felt too heavy (often requiring torch/transformers), so I wrote this lightweight, zero-dependency library to solve it. It includes strategies for context packing, PII redaction, and tool output compression. Benchmarks show it can save ~15% of tokens with negligible latency overhead (<0.5ms). Happy to answer any questions!
Dec 2025 · github.com
- 18MM
Hey HN! I’m Gui from deco (decocms.com). We’ve been using this tool internally as the foundation for a few customer AI platforms, and today we’re open-sourcing it as MCP Mesh. MCP is quickly becoming the standard for agentic systems, but… once you go past a couple servers it turns into the same problems for every team: - M×N config sprawl (every client wired to every server, each with its own JSON + ports + retries) - Token + tool bloat (dumping tool definitions into every prompt doesn’t scale) - Credentials + blast radius (tokens scattered across clients, hard to audit, hard to revoke) - No…
Dec 2025 · github.com
- 19TT
I use multiple AI tools for work and also my side projects, and the annoying part was to track my costs and token usage across tools. Everytime I had to visit each tool and its respective usage setting to check it and I was losing patience and also was getting hit by surprise limits Now I know that there are already free/open-source trackers for Cursor or Claude usage, and they are useful if that is all you need. My problem is broader as I wanted one small place to see tokens, spend, subscriptions and limits across the AI tools I actually use. I was really tired of switching tabs and…
Jul 2026 · lifehacksgermany.com
- 20OS
Hi HN, Matvey, Ildar, Joey, and Dominik here. If you're building LLM agents that use tools, you're probably worried about prompt injection attacks that can hijack those tools. We were too, and found that solutions like prompt-based filtering or secondary "guard" LLMs can be unreliable. Our thesis is that agent security should be handled at the network level between the agent and the LLM, just like a traditional web application firewall. So we built Archestra Platform: an open-source gateway that acts as a secure proxy for your AI agents. It's designed to be a deterministic firewall against…
Oct 2025 · archestra.ai
- 21
- 22OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 23SD
Hey HN! I am a FE dev who is working at a software agency and im making 2-3 estimates per week. Creating estimates is painfull manual proccess, where you have to read a lot of .docx like RFP, SRS etc. This was really tiring for me Also in agency where im working we make estimates in google spreadsheets which is another pain, trying to drag something, copy, duplicate can really mess up the whole layout So i just wanted tool that can just automate this a bit. I just started researching and I couldnt find anything good enough for my usecase. So I made a tool for creating estimates with AI. I…
2025 · devtimate.com
- 24GC
Hello HN, we're Andrew and Stephen from Keyboard (https://www.keyboard.dev/). After building AI tools for the past year, we recently made a YouTube video on building MCP servers and realized MCP is a total game-changer. It essentially lets AI do anything by connecting to your apps. But the deeper we dove, the clearer it became that security and privacy were complete afterthoughts. Coming from backgrounds at Okta and Stripe, this made us pretty uncomfortable. We kept seeing the same pattern: every app needs its own MCP server, each storing sensitive tokens, with minimal…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →