local-tools-mcp-server
A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
README
local-tools-mcp-server
A minimal, production-ready MCP server that gives AI assistants access to local file system tools — file search, directory listing, system info, and file metadata.
Built for WorkBuddy and any MCP-compatible client.
Tools
| Tool | Description |
|---|---|
localtools_search_files |
Search files by name pattern / extension with recursive depth control |
localtools_system_info |
OS, CPU, memory, uptime, user, Node.js version |
localtools_list_directory |
List directory contents with pagination and hidden-file toggle |
localtools_get_file_info |
File/directory metadata + text file preview (first 1000 bytes) |
All tools are read-only. No files are ever created, modified, or deleted.
Quick Start
Prerequisites
- Node.js >= 18
- npm >= 9
Install & Build
git clone https://github.com/YOUR_USERNAME/local-tools-mcp-server.git
cd local-tools-mcp-server
npm install
npm run build
Configure in WorkBuddy
Add to ~/.workbuddy/mcp.json:
{
"mcpServers": {
"local-tools": {
"command": "node",
"args": ["E:/path/to/local-tools-mcp-server/dist/index.js"]
}
}
}
Then activate the connector in WorkBuddy's Connector Management page.
Configure in Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"local-tools": {
"command": "node",
"args": ["/path/to/local-tools-mcp-server/dist/index.js"]
}
}
}
Usage Examples
Once connected, the AI can use these tools naturally:
"Search my D drive for all .py files, max depth 5"
"How much free memory does my system have?"
"List the contents of my Downloads folder"
"Get info on C:\projects\config.json"
Project Structure
local-tools-mcp-server/
├── src/
│ └── index.ts # All 4 tools + server entry point (~730 lines)
├── dist/ # Compiled JS output (gitignored)
├── package.json
├── tsconfig.json
└── README.md
Tech Stack
- Runtime: Node.js
- Language: TypeScript
- Validation: Zod
- Protocol: MCP TypeScript SDK
- Transport: stdio (local process, zero network config)
Security
- All file system access is read-only
- Paths are resolved and validated before any operation
- Permission errors are caught and reported gracefully
- No external dependencies beyond the MCP SDK and Zod
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.