MCP Observer Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| subscribeC | Subscribe to changes on a file or directory |
| unsubscribeC | Unsubscribe from changes on a file or directory |
| list_watchedA | List all currently monitored paths and their subscriber counts |
| subscribe_defaultB | Subscribe to the default watched.txt file for development |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| file_changes | Get a summary of recent file changes in monitored paths |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| watched.txt (dev default) |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: list_watched for viewing current subscriptions, subscribe for adding new ones, subscribe_default for a specific default case, and unsubscribe for removal. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent verb_noun pattern (list_watched, subscribe, subscribe_default, unsubscribe) with clear, action-oriented names. The naming is uniform and predictable, enhancing usability.
With 4 tools, this server is well-scoped for its purpose of monitoring file/directory changes. Each tool serves a necessary function in the subscription lifecycle, and the count is neither too sparse nor bloated.
The tool set provides complete coverage for the domain of file/directory monitoring: list (read), subscribe (create), unsubscribe (delete), and a specialized subscribe_default for convenience. There are no obvious gaps, supporting full agent workflows.