onetool
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
onetool
One MCP server in front of all the others.
What it is
onetool is an MCP server that stands in front of the MCP servers you already use. Your host program, the
assistant you talk to, sees two tools instead of hundreds: run and search.
searchfinds the tools you have, by words.runtakes a short JavaScript program that calls the real tools. The assistant writes the program, onetool runs it in a process of its own, and only the program's answer comes back. The long answers of the tools in between never reach the assistant.
You list your own servers in a settings file. onetool connects to them and offers their tools to the programs.
Related MCP server: smart-router
Install
You need Node 22 or later. A host program starts onetool with one of these two commands:
npx github:KoneEric/onetool
# once published on npm, this one too:
npx @koneeric/onetoolUntil it is published on npm, use the first.
The one option is --config, the path of the settings file. Add this entry to the MCP settings of your host
program:
{
"mcpServers": {
"onetool": {
"command": "npx",
"args": ["-y", "github:KoneEric/onetool", "--config", "/absolute/path/to/settings.json"]
}
}
}The settings file lists your own servers in the same mcpServers shape that host programs use. Paths in it are
given in full, not relative.
Try it
You can try onetool with no account and no network once the package is installed (npm ci needs the network or
npm's cache):
git clone https://github.com/KoneEric/onetool.git
cd onetool
npm ci
npm test
node bin/onetool.js --config guide/pages/settings.example.jsonThe tests run the real command against the practice server, a table of 5,000 rows with five small tools. The last command starts onetool with the example settings file, which lists the practice server. It then waits for a host program to speak to it on its standard input; press Ctrl-C to end it.
More
Install page: the settings file, rules that allow, deny or ask, the shell and files, the library of saved programs, the trail and the log, and what to do when something does not work.
Licence: MIT.
Security: how to report a weakness, and what counts as one.
Contributing: how to run the tests and send a change.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for progressive tool usage at any scale (see https://klavis.ai)
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceConsolidates multiple upstream MCP servers behind a single STDIO interface, exposing search_tools and run_tool to avoid context bloat.380 npm20MIT- AlicenseAqualityDmaintenanceA single MCP server that fronts many downstream MCP servers and Skills, exposing only four tools (search, call_tool, use_skill, admin) so that an agent's context window only ever sees search results on demand.510MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes eight SearchApi.io search engines as discrete tools, returning trimmed structured results to save context.8MIT
- AlicenseNot gradedqualityCmaintenanceFronts every MCP server you have with two tools: search shortlists relevant tools, and execute runs sandboxed Python that calls upstream tools as mcp..(). It enables agents to make bulk, repeated, or conditional tool calls using calibrated decision-model choices instead of per-item LLM generation.3MIT