gremlin-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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_commandA | Execute a shell command and return its output. The command runs through the platform shell (cmd on Windows, sh on Unix), so pipes, redirects and chained commands work. Use with care: this tool can run arbitrary commands. |
| python_codeB | Execute a Python snippet with the running interpreter. |
| python_fileC | Execute a Python script file with the running interpreter. |
| glob_filesA | Return file paths matching a glob pattern (recursive). |
| grepA | Return lines matching |
| read_fileA | Read a file's contents as UTF-8 text. |
| write_fileA | Write UTF-8 content to a file (created if missing, overwritten if present). |
| create_folderA | Create a folder, including parent folders if needed. |
| delete_folderB | Recursively delete a folder. |
| list_dirA | List the contents of a directory (name and type, sorted). |
| get_cwdA | Return the current working directory of the server process. Example: get_cwd() |
| file_infoA | Return metadata about a file or folder (type, size, modified time). |
| delete_fileA | Delete a single file. |
| append_fileB | Append text to a file, creating it first if needed. |
| move_fileC | Move or rename a file or folder. |
| copy_fileC | Copy a file to a new location. |
| replace_in_fileC | Replace all occurrences of |
| search_textA | Recursively search files under Common build/venv/cache directories are skipped automatically. |
| read_file_linesA | Read a range of lines (1-based, inclusive) from a file. Out-of-range numbers are clamped to the file's actual length. |
| get_env_varB | Return the value of an environment variable. |
| treeB | Show a tree of the directory structure up to a given depth. |
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 21 tools
Most tools have distinct purposes (file ops, command execution, code execution, search). However, `read_file` and `read_file_lines` overlap in reading file content, and `grep` vs `search_text` both search for patterns, though one is single-file and the other recursive. Minor confusion possible.
Tool names follow a consistent verb_noun pattern (e.g., `read_file`, `delete_file`, `create_folder`). Some deviations like `glob_files` and `grep` break the pattern slightly, but overall it's clear and predictable.
With 21 tools, the server covers a comprehensive set of file system operations, command execution, and code running. Each tool serves a specific need, and the count is well-suited for a general-purpose utility server without being excessive.
The tool set provides full file lifecycle (create, read, write, append, replace, move, copy, delete) plus directory management, search (glob, grep, text search), environment variable access, and code execution. No obvious gaps for the stated purpose of a file system and command execution MCP server.