read_fileLABSCO SUMMARY
Breadth in one connection, at the price of specificity.
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.
What it is
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.
What you get
- 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 —
searchandfetch - 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.yamlsuch asfilesystem,time_toolsandbrave_search, with per-group settings likeallowed_directories - A Python SDK so the same tools can be called from your own code, not only from a chat client
Requirements
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.
Setup effort
One command — bash <(curl -s https://raw.githubusercontent.com/getfounded/mcp-tool-kit/main/install.sh)
USE CASES
01
Giving an assistant a safe working directory
Point allowed_directories at one folder and let it read, write and reorganise inside it — everything else on disk stays out of reach.
02
Looking something up and writing the result down
Search the web, fetch the page, and save the extracted notes into the storage workspace in one pass.
03
Trimming a bloated tool list
Switch off the groups you never use in config.yaml so only the relevant tools ride along in the model's context.
9 tools
Listed in project docs. Your client may show a different list.
write_filelist_directorycreate_directoryrename_fileget_current_timefile_infosearchfetchBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Optional
- BRAVE_SEARCH_API_KEY in your environment
- NEWS_API_KEY in your environment
- FRED_API_KEY in your environment
- OPENWEATHER_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
bash <(curl -s https://raw.githubusercontent.com/getfounded/mcp-tool-kit/main/install.sh)MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-tool-kit": {
"command": "docker",
"args": [
"exec",
"-i",
"mcp-server",
"python",
"mcp_server_v2.py"
]
}
}
}The configuration on this page does not set BRAVE_SEARCH_API_KEY, NEWS_API_KEY, FRED_API_KEY or OPENWEATHER_API_KEY. This project documents them in a .env file in the project folder (copy .env.template to .env), and each is needed only by the tool group that uses it.
