fsguard-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fs_readA | Read a text file's contents. path is relative to FSGUARD_ROOT. |
| fs_writeA | Write (creating or overwriting) a text file. Parent directories are created as needed, but only within FSGUARD_ROOT. |
| fs_listA | List the entries of a directory, each tagged file or directory. |
| fs_searchA | Find files matching a glob pattern (e.g. '*.py') under path, recursively. Any match that resolves outside FSGUARD_ROOT — e.g. via a symlink — is silently excluded rather than reported. |
| fs_moveA | Move or rename a file/directory. Both source and destination must resolve within FSGUARD_ROOT. If destination already exists as a file, it is overwritten. If destination already exists as a directory, the call fails instead of moving source inside it. |
| git_init_repoA | Initialize a new git repository at repo_path (relative to FSGUARD_ROOT). |
| git_repo_statusB | Show staged, unstaged, and untracked files for a repo. |
| git_stageA | Stage files for commit. Every path is validated against FSGUARD_ROOT before being staged — a path that would escape the root fails the whole call, staging nothing. |
| git_commit_repoC | Commit staged changes. author must be 'Name '. |
| git_diff_repoC | Show the diff for a repo's working tree (or staged changes). |
| git_log_repoC | Show recent commit history. |
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 11 tools
Each tool targets a distinct operation: file read, write, list, search, move; git init, status, stage, commit, diff, log. There is no overlap or ambiguity between tools, enabling reliable selection.
The naming follows a consistent fs_/git_ prefix pattern with action-oriented verbs. Minor deviation like 'git_repo_status' vs 'git_stage' (noun-verb vs verb-only) creates slight inconsistency but remains predictable.
11 tools cover file system and git operations without redundancy. The scope is well-balanced—enough to handle common workflows without overwhelming the agent.
The file system layer includes create, read, update, list, search, and move, but lacks a delete operation, which is a notable gap. Git coverage is solid for basic workflows but omits branch operations. Overall, a reasonable surface for the intended guarded-root use case.