Toolmesh
Self-hosted MCP gateway that turns REST APIs into tools with auth, policies and audit
- Platforms
- self-hosted, API
- Runs
- Remotely
- Version
- 0.6.0
- Listing updated
- today
Similar MCP servers
About Toolmesh
Toolmesh is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
Think of it as a key vault and checkpoint between agents and your systems. Clients connect to one MCP endpoint, while ToolMesh keeps the API keys in its own environment, adds them at call time and checks with OpenFGA whether the caller may use that tool. Every call, including denied and failed ones, produces an audit entry, stored as log lines or in SQLite.
REST backends are described in DADL files, a few lines of YAML per endpoint, and the DADL registry offers descriptions for 36 APIs. Existing MCP servers over HTTP or stdio can sit behind the same endpoint, with tools named backend_tool. Optional JavaScript policies check parameters before a call and filter results afterwards, for example to redact personal data.
In Code Mode the model sees only two tools, discover_tools and execute_code, then writes short JavaScript to chain calls in one round trip. The project is at version 0.x and runs with Docker Compose alongside KeyDB; a public demo serves Hacker News APIs.
Tools this server provides (2)
Taken from the project documentation; the running server may differ.
- discover_tools
- Looks up tool signatures in Code Mode.
- execute_code
- Runs short JavaScript that makes several tool calls.
What it does
- DADL REST wrapping
- Describe an API in YAML and expose it as MCP tools.
- Server-held credentials
- Keys never appear in prompts or client config.
- OpenFGA authorization
- Grants by user, role, backend, tool or access class.
- Audit log
- One entry per call with caller, parameters and outcome.
- Code Mode
- Two tools let the model script many calls at once.
- JavaScript policies
- Pre-call checks and result filtering.
Good for
- Give agents access to internal REST APIs without sharing keys
- Audit which tool an agent called and with what
- Restrict a team to read-only tools
- Put several MCP servers behind one endpoint
Toolmesh FAQ
How do I run it?
With Docker Compose; it starts ToolMesh and KeyDB and listens on port 8123 by default.
What authenticates clients?
OAuth 2.1 or an API key.
Is it stable?
The README says it is at version 0.x and minor releases can change configuration.
Can I try it first?
Yes, a public demo at demo.toolmesh.io serves the Hacker News APIs.
What are the best alternatives to Toolmesh?
The closest alternatives to Toolmesh are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.


