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. |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxwellplanck/mcp-lock-manager'
If you have feedback or need assistance with the MCP directory API, please join our Discord server