mcp-filesearch
Currently it only exposes a datetime liveness probe; the README describes planned read-only root-scoped ripgrep search tools that are not yet in the schema.
Get the current date and time in a specified IANA timezone (default UTC).
Shift the result by whole days, from -365 to +365.
Request output as ISO 8601 wall-clock time, Unix epoch seconds, or a localized human string.
Receive
iso,unix, and canonicaltimezone, plushumanwhen requested.Future/planned: bounded file listing, match counting, and content search over allowed roots, read-only and root-scoped.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-filesearch find all TypeScript files modified in the last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-filesearch
A read-only, root-scoped filesystem search MCP server. It wraps ripgrep (rg) behind a small set of bounded tools — file listing, match counting, content search — always confined to the roots passed on the command line: never a shell, never a write.
Status: under construction, phase by phase. docs/implementation-plan.md is the canonical plan and records what has landed. Today the server ships get_datetime as its liveness probe; the search tools arrive phase by phase behind the security rules in CONVENTIONS.md.
Requirements
Node ≥ 22; CI runs 22 and 24, and .node-version pins 24 for local mise users. The search tools spawn rg, which CI runners ship.
Related MCP server: File Search Tool
Develop
npm ci
npm run build
npm testnpm test runs vitest against src/ through the SDK's own client over an in-memory transport, so no build is needed to test. npm run build is needed for the bin entry and for npx over GitHub.
Run
node dist/index.js /path/to/search [another/root ...]At least one allowed root is required — there is no default and no cwd fallback. Roots are realpathed at startup and duplicates collapse; every path a tool touches is validated against them before anything runs.
Register with 1MCP
"filesearch": {
"command": "npx",
"args": ["-y", "github:GwylimWilliams/mcp-filesearch", "/path/to/search"],
"tags": ["notes", "search"]
}Scoped roots are passed as CLI args after the repo — never cwd, so the scoping holds whatever directory the gateway happens to run in. The prepare script builds on install, which is what makes npx -y github:… work without a published package.
The rules
CONVENTIONS.md— the canonical rule listAGENTS.md— the same rules agent-facing, plus the per-tool checklistdocs/adding-a-tool.md— the worked walkthroughSECURITY.md— the security posture and how to report a problem
License
MIT.
Available Tools
1 toolget_datetimeGet date and timeARead-only
Current date and time in an IANA timezone, optionally shifted by whole days. The iso field is the wall clock in that zone, so its offset makes the instant unambiguous; unix is the same instant as epoch seconds, and human is a localized rendering.
Inputs: format, timezone, offsetDays. Returns: iso, unix, human, timezone
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
The server exposes only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly stated as retrieving current date and time.
The single tool name get_datetime follows a clear snake_case verb_noun convention. There are no other names to conflict with or create inconsistency.
The server is named mcp-filesearch, but it provides only a datetime tool, which is unrelated to file search. A single trivial tool is an extreme mismatch for the apparent file-search purpose.
For a file-search server, there are no tools for searching, reading, listing, or retrieving files. The surface is severely incomplete and cannot support the stated domain.
Maintenance
Related MCP Connectors
Read-only search of the Agent Connectors MCP directory.
Search and manage your team's knowledge from MCP clients.
Search and get install details on MCP servers, right from your agent -- a unified marketplace index.
Browse and manage files in your Moxt AI workspace from any MCP client.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables file and directory searching through the greply CLI tool with configurable search options like context lines, case sensitivity, and pattern matching. Provides direct access to powerful grep-like functionality from MCP-compatible clients.213 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables file system search and inspection, including directory listing, regex-based file name and content searches, and reading text, PDF, and DOCX files.1MIT
- FlicenseAqualityDmaintenanceEnables listing, reading, and searching local files and directories through MCP tools.4-
- AlicenseAqualityDmaintenanceA personal file-indexing MCP server that provides semantic and keyword search over a file index, plus file content lookup and browsing. It enables agents to search and retrieve files from a user's home directory.4MIT