To

ToolMesh – turn all your REST APIs into MCP tools via declarative YAML

Hacker News

ToolMesh – turn all your REST APIs into MCP tools via declarative YAML

When at night the pager goes off, I ask Claude: "what is alerting, what changed in the last hour?". Claude answers by chaining calls across Graylog, Prometheus, Alertmanager, Linode, GitLab, NetBox and more. The menu of tools Claude has access to is even bigger than that: I have connected 30 backends so far (20 in the public registry, the rest internal to my setup), including most of my ops stack (OPNsense, Tailscale, Xen Orchestra, DokuWiki and more). ToolMesh is what makes that menu composable for Claude. Each backend is a simple DADL file - a small YAML that declares the REST API of the service to ToolMesh, which then exposes those tools to Claude. Most of the publicly available DADLs (currently 20 with 1,833 tools in total) were drafted by an LLM in minutes and tuned from there. The registry is public. Here is the HN API as DADL - the API behind this very page: tools: get_top_stories: method: GET path: /topstories.json access: read description: "Up to 500 top story IDs, ordered by HN ranking" get_item: method: GET path: /item/{id}.json access: read description: "Get story, comment, job, poll, or pollopt by ID" params: id: { type: integer, in: path, required: true } How can a single agent access so many backends without creating context overflow? Code Mode. Naively, every tool and schema goes into context - 50,000+ tokens before the agent does anything useful. ToolMesh compresses that to ~1,000 by giving the model a typed API surface and letting it ask for endpoint details only when it needs them. That is the difference between "doesn't scale" and "please add 10 more, it's fine!". ToolMesh can also connect to other MCP servers, rendering them code mode capable as well. Security in mind: credentials never reach the model (they are injected at runtime). ToolMesh runs a fail-closed pipeline: auth -> authz -> credential injection -> exec -> output gate -> audit. CallerClass lets the same API have different policy per client type (local dev assistant vs hosted agent vs CI bot). Every call lands in a SQLite-queryable audit log - "what did the agent do Tuesday?" becomes a SQL query, not a shrug. ToolMesh is not magic. APIs with stateful flows or weird auth still need care, and an LLM with a great tool surface can still pick the wrong tool. You still need sane policy. Try before cloning: https://demo.toolmesh.io is a public instance with the HN API loaded (login dadl/toolmesh). Connect Claude Desktop, Claude Code, or ChatGPT in 30 seconds: https://toolmesh.io/demo GitHub: https://github.com/DunkelCloud/ToolMesh Docs: https://toolmesh.io DADL Spec + Registry: https://dadl.ai Apache 2.0, single Go binary or Docker, no SaaS dependency. If you think of your full ops stack - what DADLs would you like to have available to your LLM?

Share card

Actual performance

2points
2comments
Did not reach leaderboard

Launch Intel predictions

Analyze your own launch →
Product HuntOn track for Day 1 leaderboard · Strong signals: agent, claude, model · Missing: mac, agents, macos
94%94% predicted probability of success on Product Hunt, based on ML models trained on real launch data.
best fitHighest predicted score across all platforms for this description.
Indie HackersFits the IH revenue-focused audience · Strong signals: para, including · Missing: supports, reddit linkedin, podcasting
75%75% predicted probability of success on Indie Hackers, based on ML models trained on real launch data.
TrustMRRLess likely to generate early MRR · Strong signals: answers, para · Missing: mobile apps, ios, personal
39%39% predicted probability of success on TrustMRR, based on ML models trained on real launch data.
Hacker NewsMay not resonate with HN audience · Strong signals: pipe, 000, io · Missing: https docs, excited, just released
37%37% predicted probability of success on Hacker News, based on ML models trained on real launch data.
nativeThis product was originally launched on this platform.
AppSumoMay struggle as an AppSumo deal · Strong signals: host, calls · Missing: plus, platform, intuitive
33%33% predicted probability of success on AppSumo, based on ML models trained on real launch data.
Acquire.comPre-revenue stage for this audience · Strong signals: saas · Missing: arr, mrr, revenue
23%23% predicted probability of success on Acquire.com, based on ML models trained on real launch data.
BetaListMay not resonate with beta-testers · Strong signals: chat · Missing: web3, crypto, cryptocurrency
0%0% predicted probability of success on BetaList, based on ML models trained on real launch data.

Correct prediction on native model

Similar products

Ru
Ruby on Roda – REST APIs with Roda and Sequel48%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Ruby on Roda – REST APIs with Roda and Sequel

Hacker News1
Sheetfy
Sheetfy51%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Turn your spreadsheets into REST APIs

Indie Hackers1$784/moanalytics
Fe
Fern, a language for defining REST APIs that compiles into OpenAPI66%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Fern, a language for defining REST APIs that compiles into OpenAPI

Hacker News18
Ex
Expressa – build REST apis without code56%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Expressa – build REST apis without code

Hacker News8
Ea
Easily consume REST APIs with Go49%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Easily consume REST APIs with Go

Hacker News51
Te
Testing REST, GraphQL APIs61%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Testing REST, GraphQL APIs

Hacker News14
Wu
WunderGraph – Aggregate REST and GraphQL APIs, Add AuthN/Z and Caching76%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

WunderGraph – Aggregate REST and GraphQL APIs, Add AuthN/Z and Caching

Hacker News9
Co
Codeless Tests for GraphQL and REST APIs59%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Codeless Tests for GraphQL and REST APIs

Hacker News2
Isthmus
Isthmus48%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

Connecting REST APIs

Indie Hackers1apis
PS
PSX – Build fully typed REST APIs64%Launch Intel prediction score: how likely this product is to succeed on its source platform, based on its name, tagline, and description.

PSX – Build fully typed REST APIs

Hacker News3