MCP Enhanced Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP host | 127.0.0.1 |
| MCP_PORT | No | HTTP port | 3000 |
| MCP_TRANSPORT | No | Transport: stdio or http | stdio |
| MCP_AUTH_TOKEN | No | Bearer token for auth (optional) |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read the contents of a file from the local filesystem |
| write_fileA | Write content to a file on the local filesystem. DESTRUCTIVE - overwrites existing files. |
| list_directoryA | List the contents of a directory |
| delete_fileA | Delete a file from the local filesystem. DESTRUCTIVE and NON-IDEMPOTENT. |
| search_codeB | Search for a pattern in code files using regex |
| run_commandB | Execute a shell command. DESTRUCTIVE operation with side effects. |
| confirm_actionA | Request user confirmation before a destructive or important action. |
| request_inputA | Request additional input from the user during tool execution. |
| task_statusB | Get the status of an async task |
| task_cancelA | Cancel a running async task |
| task_listA | List all tasks and their statuses |
| batch_processB | Start a batch processing task. Returns a task ID for polling. |
| get_weatherA | Get current weather data for a location |
| system_infoB | Get system information |
| list_available_resourcesA | List all available MCP resources as resource links |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_review | Review code for quality, bugs, and improvements |
| explain_code | Explain what a piece of code does |
| generate_tests | Generate unit tests for the given code |
| debug_error | Debug an error in code |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info | Information about this MCP server |
| config-info | Current server configuration and environment |
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose, but the presence of get_weather and system_info alongside file and task management tools creates ambiguity about the server's core domain, potentially confusing an agent.
Most tools use a verb_noun pattern (e.g., read_file, list_directory), but several tools like task_status and system_info use noun_noun, breaking the pattern. The mix is readable but inconsistent.
15 tools is a reasonable count, but the inclusion of get_weather and system_info seems extraneous for the implied focus on file and task management, making the set feel slightly over-scoped.
File operations lack create directory, move, and copy; task management lacks a create_task tool (tasks are only created via batch_process). These gaps could cause agent failures in common workflows.