
OneTool MCP
OneTool solves the MCP token tax problem by exposing 100+ tools through a single server instead of dozens. Instead of loading tool definitions that burn 3K-30K tokens per server, your agent writes Python code like `__run brave.search(query="react docs")` to call tools on demand. You get Brave search, Google Grounding, Tavily, Context7 docs, database queries, Excalidraw diagrams, file operations, Excel handling, Playwright browser automation, and Chrome DevTools utilities all from one connection. It includes smart context stores backed by SQLite FTS5, image vision routing to cheaper models, and LLM-powered text compaction. The architecture cuts token overhead by 96% compared to running separate MCP servers for each capability, which matters when you're paying per million tokens.
- GitHub stars
- 20
- tool
- 1
- last updated
- Apr 3, 2026
Tools
1 toolsPublic tool metadata for what this MCP can expose to an agent.
onetoolSingle MCP tool that executes Python code; packs and proxied servers are called from within it.
Single MCP tool that executes Python code; packs and proxied servers are called from within it.
No parameter schema in public metadata yet.
Sponsors
Readme
🧿 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.
Works with Claude Code, Cursor, Codex - any MCP client
The Problem
Details
- Repository
- github.com/beycom/onetool-mcp
- Website
- onetool.beycom.online
- Categories
- Web & Browser Automation, Cloud & Infrastructure, Developer Tools, Design & Creative, Search & Web Crawling
- Registry
- MCP registry, active