BIbingwu1995·Aug 1, 2025
In Ask HN: Is manually discovering and configuring MCP servers the only way?aipotheosis-labs
aci
Python2025–2025
aipotheosis-labs / aci
aci
ACI.dev is the open source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent through direct function calling or a unified MCP server. The birthplace of VibeOps.
3Distinct people
4Mentions
0Explicit recommenders
4.9KGitHub stars
What to know before exploring
What it is
ACI.dev is the open source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent through direct function calling or a unified MCP server. The birthplace of VibeOps.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week4 dated mentions
Observed mentions: 2025-04-28 12:58:55 UTC to 2025-08-01 13:22:49 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 28 | 2025-04-28 00:00:00 UTC | 2025-05-05 00:00:00 UTC | 3 | 2 | 1 |
| May 5 | 2025-05-05 00:00:00 UTC | 2025-05-12 00:00:00 UTC | 0 | 0 | 0 |
| May 12 | 2025-05-12 00:00:00 UTC | 2025-05-19 00:00:00 UTC | 0 | 0 | 0 |
| May 19 | 2025-05-19 00:00:00 UTC | 2025-05-26 00:00:00 UTC | 0 | 0 | 0 |
| May 26 | 2025-05-26 00:00:00 UTC | 2025-06-02 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2 | 2025-06-02 00:00:00 UTC | 2025-06-09 00:00:00 UTC | 0 | 0 | 0 |
| Jun 9 | 2025-06-09 00:00:00 UTC | 2025-06-16 00:00:00 UTC | 0 | 0 | 0 |
| Jun 16 | 2025-06-16 00:00:00 UTC | 2025-06-23 00:00:00 UTC | 0 | 0 | 0 |
| Jun 23 | 2025-06-23 00:00:00 UTC | 2025-06-30 00:00:00 UTC | 0 | 0 | 0 |
| Jun 30 | 2025-06-30 00:00:00 UTC | 2025-07-07 00:00:00 UTC | 0 | 0 | 0 |
| Jul 7 | 2025-07-07 00:00:00 UTC | 2025-07-14 00:00:00 UTC | 0 | 0 | 0 |
| Jul 14 | 2025-07-14 00:00:00 UTC | 2025-07-21 00:00:00 UTC | 0 | 0 | 0 |
| Jul 21 | 2025-07-21 00:00:00 UTC | 2025-07-28 00:00:00 UTC | 0 | 0 | 0 |
| Jul 28 | 2025-07-28 00:00:00 UTC | 2025-08-04 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesGitHub Trending: open-source infra to power Unified MCP servers
1 points · Open discussionI'm working on an unified MCP server that can search and use a large number of tools. The current way of using MCP server (adding each MCP server directly) simply doesn't scale.
If your AI agent needs to use 100 tools, you need to manually configure a lot of MCP servers. And when you feed those tools to the LLM, it may get confused and tool calling accuracy starts to drop.
This is why I'm building a unified MCP server with just two meta tools:
- Search Available tools
- Execute a tool
When I want to send an email, I ask LLM to use the Search Meta tool to search for Gmail related tools in the backend, then the meta tool returns the description of relevant tools. The LLM then uses the Execute meta tool to actually use the gmail tool returned.
https://github.com/aipotheosis-labs/aci
In Ask HN: What are you working on? (April 2025)Show HN: Open-Source Infra for a Single MCP Server to Search and Use 600 Tools
41 points · Open discussion