Filesystem Watcher MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| watch_directoryB | Start watching a directory for file system events. Returns a |
| poll_eventsA | Drain and return queued file system events. Events are removed from the queue once returned (consume-once semantics). Call repeatedly to receive all pending events. |
| list_active_watchesA | Return a list of all currently active directory watches. Each entry includes the |
| unwatchB | Stop and remove an active directory watch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: starting, listing, polling, and stopping watches. No overlap or ambiguity.
All tools use verb_noun snake_case pattern. 'unwatch' is slightly non-standard but still clear and consistent.
4 tools is appropriate for a filesystem watcher, covering all essential operations without being too many or too few.
Covers full lifecycle: create (watch_directory), read (list_active_watches, poll_events), delete (unwatch). No obvious gaps for basic watching.