OneTool MCP
Replace a pile of separate MCP configs with one server that bundles search, docs, cloud, diagrams, databases, GitHub, devtools, and Playwright for daily agent-driven development.
Overview
OneTool MCP is a MCP server for the Build phase that bundles Brave, Google, Tavily, Context7, AWS, Excalidraw, database, GitHub, DevTools, and Playwright into one agent integration.
What is this MCP server?
- Single MCP aggregating Brave, Google, and Tavily search
- Context7 and dev-oriented doc lookup in the same server (version 2.2.2)
- AWS, database, and GitHub tooling for infra and repo operations from the agent
- Excalidraw and Playwright coverage for diagrams and browser automation
- DevTools bundle aimed at reducing per-integration MCP boilerplate for solo devs
- Advertised bundle: Brave, Google, Tavily, Context7, AWS, Excalidraw, DB, GitHub, DevTools, Playwright (10 named capabili
- Server version 2.2.2 in server manifest
- Repository: github.com/beycom/onetool-mcp
Community signal: 20 GitHub stars.
What problem does it solve?
Solo builders waste hours duplicating MCP configs and credentials across a dozen single-purpose servers just to code with an agent.
Who is it for?
Indie devs who want one MCP hub while building full-stack or agent-assisted products and already use several of the bundled services.
Skip if: Minimal-security environments that require one MCP per vendor, or builders who only need a single API (e.g. GitHub alone).
What do I get? / Deliverables
One registered OneTool MCP connection gives your agent unified access to the listed dev, search, cloud, and browser tools during implementation.
- Unified agent access to listed search, cloud, repo, DB, diagram, and browser tools
- Fewer MCP config files to maintain across projects
- Faster iterative build loops without swapping MCP servers per task
Recommended MCP Servers
Journey fit
Consolidated dev tooling matters most while you are building and wiring external services, even though some tools also help during validate prototypes. Integrations subphase is the canonical shelf because OneTool’s value is connecting one agent session to many third-party capabilities.
How it compares
All-in-one dev MCP aggregator, not a focused RDL or mobile-UI specialty server.
Common Questions / FAQ
Who is OneTool MCP for?
Solo developers using Claude Code, Cursor, or similar agents who want search, docs, AWS, DB, GitHub, diagrams, and Playwright behind one MCP.
When should I use OneTool MCP?
Use it during Build integrations when your agent routinely hits multiple external tools in one session and you want one config instead of many.
How do I add OneTool MCP to my agent?
Follow setup on onetool.beycom.online and github.com/beycom/onetool-mcp, then add the server entry your client expects with API keys for the providers you enable.