<strong>🧿 One MCP for developers - no tool tax, no context rot. 250+ tools your agent calls as Python code: search, docs, files, databases
🧿 One MCP for developers - no tool tax, no context rot. 250+ tools your agent calls as Python code: search, docs, files, databases, diagrams, vision, memory - plus a proxy for every MCP server you already use.. That is what the onetool mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 14 tools. What each one is for:
Pack — Toolsarch — generate, validate, bundle_solution, …brave — search, news, image, video, search_batchchrome_util — highlight_element, guide_user, …context7 — search, docconvert — pdf, word, powerpoint, excel, autodiagram — render_diagram, batch_render, get_template, …excel — read, write, formula, create_table, … (24 tools)file — read, write, edit, grep, slice, toc, … (16 tools)ground — search, dev, docs, reddit, search_batchknowledge — search, ask, write, related, … (15 tools)localhist — save, diff, restore, autosave_start, … (15 tools)The server ships on npm as skills, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: DO_NOT_TRACK, PRIVATE_MCP_URL, PRIVATE_MCP_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Onetool MCP's toolset — Pack, arch, brave and 11 more — is a fair guide to whether it matches your workflow. It is maintained by beycom; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Onetool MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Pack | Tools |
| arch | generate, validate, bundle_solution, … |
| brave | search, news, image, video, search_batch |
| chrome_util | highlight_element, guide_user, … |
| context7 | search, doc |
| convert | pdf, word, powerpoint, excel, auto |
| diagram | render_diagram, batch_render, get_template, … |
| excel | read, write, formula, create_table, … (24 tools) |
| file | read, write, edit, grep, slice, toc, … (16 tools) |
| ground | search, dev, docs, reddit, search_batch |
| knowledge | search, ask, write, related, … (15 tools) |
| localhist | save, diff, restore, autosave_start, … (15 tools) |
| mem | write, search, ask, history, rollback, … (31 tools) |
| ot_forge | create_ext, validate_ext |
{
"mcpServers": {
"onetool": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"DO_NOT_TRACK": "your-value",
"PRIVATE_MCP_URL": "your-value",
"PRIVATE_MCP_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DO_NOT_TRACK | Configuration value read at startup. | Optional |
| PRIVATE_MCP_URL | Endpoint or connection string the server talks to. | Yes |
| PRIVATE_MCP_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.