The appeal is not any single capability — it is that files, time, search, browsing and document work arrive through one server with one config file, instead of five separate entries in your client. The published per-group pages are still outlines, so the reliable way to see what you actually have is to start it and ask the client to list its tools; `config.yaml` is then where you turn the noise back down.
A toolkit server with dynamic tool registration: tool groups are discovered and registered at runtime, and a `config.yaml` decides which of them are switched on. It runs over stdio for Claude Desktop, or over SSE on `http://localhost:8080` for browser-based access.
- Filesystem work confined to one directory: `read_file`, `write_file`, `list_directory`, `create_directory`, `rename_file`
- Time and timezone operations through `get_current_time`
- Web search backed by Brave Search, plus page retrieval — `search` and `fetch`
- Playwright-based browser control
- Document handling for PDF, Excel and PowerPoint, and data pulls from Yahoo Finance, FRED and World Bank
- Group-level switches in `config.yaml` such as `filesystem`, `time_tools` and `brave_search`, with per-group settings like `allowed_directories`
- A Python SDK so the same tools can be called from your own code, not only from a chat client
A one-line install script per platform, or the Docker image `ghcr.io/getfounded/mcp-tool-kit:latest` — Docker is what the launcher drives either way. Keys go in `.env` and are only needed by the group that uses them: `BRAVE_SEARCH_API_KEY`, `NEWS_API_KEY`, `FRED_API_KEY`. File operations are restricted to a dedicated storage directory (`~/mcp-tool-kit-storage` on macOS and Linux) with `documents`, `downloads` and `workspace` inside it.
One command plus a key — bash <(curl -s https://raw.githubusercontent.com/getfounded/mcp-tool-kit/main/install.sh), then supply credentials