exec-dir-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | 在指定文件夹中执行命令。默认目录: /app |
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 1 tool
With only one tool, there is no risk of confusion or misselection between tools. The single tool has a clear, singular purpose of executing commands in a specified directory.
With only one tool, there is no pattern to assess beyond the single name itself. 'execute_command' is a reasonable verb_noun name, but consistency cannot truly be evaluated with a single data point.
A server with a single tool feels extremely thin for a directory-execution MCP server. One would expect at least listing directory contents, reading files, or inspecting the environment alongside command execution.
The tool provides command execution, but a directory-execution server would plausibly benefit from related operations like listing directory contents, checking working directory, or managing paths. With only execute_command, the surface is quite limited and likely to create dead ends.