File Opener MCP 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 |
|---|---|
| open_fileA | Open a file or directory using the system default application (macOS open command) |
| reveal_in_finderB | Reveal a file or directory in Finder |
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 2 tools
The two tools have clearly distinct purposes: open_file opens files with the default application, while reveal_in_finder shows files in Finder without opening them. There is no overlap or ambiguity between these functions, making tool selection straightforward.
Both tools follow a consistent verb_noun pattern (open_file, reveal_in_finder) with clear, descriptive names. The naming style is uniform and predictable across the tool set.
With only two tools, the server feels thin for a 'File Opener' domain. While the tools cover basic macOS file operations, the scope suggests potential gaps (e.g., no tools for editing, copying, or managing files), making the set appear underdeveloped.
The tool set is severely incomplete for file operations. It lacks core functionalities like creating, deleting, moving, or editing files, and is limited to macOS-specific actions. This will cause agent failures for common file management tasks beyond opening or revealing.