Back to DirectoryCOMPARISON OVERVIEW
"Local tools" MCP servers run on your workstation, access local resources, and avoid cloud API keys. All active official reference servers except Fetch are local-first; Fetch is the hybrid that calls outbound HTTP.
LOCAL FILE OPERATIONS: FILESYSTEM
npx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir
Fourteen tools for read/write/search/tree operations confined to allowlisted directories (or MCP Roots). No cloud account required.
LOCAL GIT: GIT MCP
uvx mcp-server-git --repository path/to/git/repo
Operates on local .git metadata and working tree. No GitHub token needed for local history.
LOCAL CLOCK: TIME
uvx mcp-server-time
Timezone math locally — no network.
LOCAL STATE: MEMORY
npx -y @modelcontextprotocol/server-memory
Persists knowledge graph on local disk (see Memory README for storage details).
FETCH — LOCAL PROCESS, REMOTE DATA
uvx mcp-server-fetch
Process runs locally; tool fetches remote URLs. Include when "local tools" means "no SaaS API keys" but web access is OK.
COMPARISON TABLE
| Server | Network needed? | API key? |
| Filesystem | No | No |
| Git | No (local repo) | No |
| Time | No | No |
| Memory | No | No |
| Fetch | Yes (HTTP) | No |
VS COMMUNITY CLOUD SERVERS
Slack, Google Drive, and GitHub reference servers archived or moved to vendors — they required OAuth tokens. Official local reference set keeps onboarding friction low.
SECURITY ADVANTAGE
Local allowlists reduce exfiltration to arbitrary cloud accounts — but Filesystem write tools can still destroy local files. Combine scope limits with client tool approval.
DECISION GUIDE
Air-gapped or privacy-sensitive dev: Filesystem + Git + Time + Memory, skip Fetch. Documentation-heavy local work: add Fetch.
Best MCP Servers for Local Tools
Run utilities on your machine through MCP without cloud dependencies.