Universal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Server mode: 'stdio' for Claude Desktop or 'http' for OpenAI/web integration | stdio |
| MCP_API_KEY | No | API key for authentication in HTTP mode (optional but recommended for production) | |
| MCP_HTTP_HOST | No | Host address for HTTP mode | 0.0.0.0 |
| MCP_HTTP_PORT | No | Port number for HTTP mode | 3000 |
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 |
|---|---|
| write_fileC | Write content to a file |
| delete_fileC | Delete a file |
| search_filesC | Search for files containing specific text |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| File Resource | Read a file by key |
| File List | List all available files |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: delete_file removes files, search_files finds files based on content, and write_file creates or modifies files. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (delete_file, search_files, write_file) using snake_case throughout. This predictability enhances readability and usability for agents.
With only 3 tools, the server feels thin for a 'Universal MCP Server' name, suggesting it might lack broader functionality. However, for basic file operations, the count is borderline but manageable, as it covers core actions without being excessive.
The tool set is significantly incomplete for file operations, missing essential actions like read_file or list_files, which are critical for a comprehensive file management system. This gap will likely cause agent failures when trying to access or list file contents.