MCP Opener
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_OPENER_BROWSER | No | Preferred browser: 'firefox' | 'chrome' | 'chromium' | 'default' | default |
| MCP_OPENER_TMP_COPY | No | Whether to copy files to /tmp for Flatpak access | true |
| MCP_OPENER_FIREFOX_FLATPAK | No | Explicitly set if Firefox is installed via Flatpak (auto-detected if omitted) |
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_folderA | Open a folder in the system file manager (Nautilus, Finder, Explorer, etc.) |
| open_fileB | Open a file with its default application |
| open_browserA | Open a URL in the preferred web browser. Supports Firefox (including Flatpak), Chrome, and system default. |
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 3 tools
Each tool has a clearly distinct purpose: open_browser for URLs, open_file for files, and open_folder for directories. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the target type.
All tool names follow a consistent verb_noun pattern (open_browser, open_file, open_folder) with the same verb 'open' and descriptive nouns. This uniformity enhances readability and predictability.
With 3 tools, the server is well-scoped for its purpose of opening resources (URLs, files, folders). Each tool earns its place by covering a distinct aspect of the domain without redundancy or bloat.
The tool surface is complete for the domain of opening resources, covering URLs, files, and folders. There are no obvious gaps, as these three categories encompass the typical use cases for an opener utility.