Secure Local Workspace 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnosticsA | Check configuration and safety capabilities before starting local project work. |
| list_projectsA | List the local projects, write permissions, and task names authorized by the user. |
| discover_projectsA | Find Git repositories and common non-Git project folders only beneath parent folders that the user approved locally during setup. |
| connect_projectA | Authorize one directory beneath a locally approved discovery root. Non-Git projects can be edited, but commit and push are automatically disabled. |
| disconnect_projectA | Remove one project from the MCP authorization list without deleting any project files. |
| list_filesB | List files and directories beneath an authorized project path. |
| read_fileB | Read a bounded line range from a text file and return its SHA-256 edit precondition. |
| search_textA | Search for a literal string across bounded text files in an authorized project. |
| apply_patchA | Apply a unified diff to one existing text file after verifying the SHA-256 returned by read_file. |
| create_text_fileB | Create a new text file without overwriting an existing path. |
| delete_text_fileA | Delete one regular text file only after verifying the latest SHA-256 returned by read_file. |
| git_statusB | Run a fixed, read-only Git status command in an authorized project. |
| git_diffB | Run a fixed, read-only Git diff command in an authorized project. |
| git_unstageA | Remove explicit paths from the Git index without changing their working-tree contents. |
| git_commitB | Stage and commit only explicit relative paths after status review, concurrency validation, whitespace checks, and sensitive-content scanning. |
| git_pushA | Push the reviewed current commit without force to an allowlisted remote and branch. This must be enabled locally per project. |
| run_taskA | Run one task whose executable and arguments were explicitly configured by the user. |
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 17 tools
Each tool targets a distinct operation—project discovery/auth, file read/write, git workflow, or task execution—so an agent can reliably select based on action. The only mild pairing is list_projects vs discover_projects, but their descriptions clearly separate authorized projects from available ones.
Most tools follow a predictable verb_noun pattern like list_files, read_file, apply_patch, and run_task. diagnostics is a noun-style outlier, and the git_* family uses command nouns (git_status, git_diff) rather than verbs, but the overall pattern remains recognizable.
At 17 tools, the server is slightly above the typical 3–15 range, but the count is justified by covering project discovery, authorization, file editing, git operations, and task execution. Each tool earns its place and none feel redundant.
The toolset covers project lifecycle, file CRUD/search, core git commit/push workflows, and configured task execution with no dead ends. Minor gaps like file rename/move or git branch/log operations are not essential to the secure workspace purpose but could be nice additions.