mcp-lock-manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | The project root directory. If not set, defaults to the current working directory. Alternatively, you can pass --project-root as a command-line argument. |
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 |
|---|---|
| lock_acquireA | Acquire exclusive file locks. Fails with conflict details if any path is held by another live session. Always call this before editing files. |
| lock_releaseA | Release file locks. If paths are omitted, releases ALL locks for this session. |
| lock_listA | List all current file locks with owner, PID, timestamp, and alive status. |
| lock_cleanupA | Force-remove all stale locks (dead PIDs). Use when lock_list shows locks with alive: false. |
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 4 tools
Each tool has a distinct purpose: acquire, release, list, and cleanup locks. No two tools overlap in functionality.
All tools follow a consistent verb_noun pattern (e.g., lock_acquire, lock_list), making them highly predictable.
Four tools cover the essential operations of a lock manager without unnecessary additions or gaps.
The set provides full lifecycle management: acquire, release (including bulk), list, and cleanup of stale locks. No obvious missing operations.