lock_acquire — work-access-tools MCP Tool
lock_acquire
(lock acquire) is one of 4 tools on the
work-access-tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lock_acquire from your client
- Claude Code work-access-tools lock_acquire run in your project directory
- Claude Desktop work-access-tools lock_acquire ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor work-access-tools lock_acquire ~/.cursor/mcp.json
- VS Code work-access-tools lock_acquire .vscode/mcp.json
- Zed work-access-tools lock_acquire ~/.config/zed/settings.json
- Windsurf work-access-tools lock_acquire ~/.codeium/windsurf/mcp_config.json
- Cline work-access-tools lock_acquire ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI work-access-tools lock_acquire ~/.gemini/settings.json
- Grok work-access-tools lock_acquire .mcp.json (in your project root)
- ChatGPT work-access-tools lock_acquire Settings → Connectors → Advanced → Developer mode
- Claude.ai work-access-tools lock_acquire Settings → Connectors → Add custom connector
- LangChain work-access-tools lock_acquire pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http work-access-platform https://work-access-platform.bfurrow26.workers.dev/mcp/c/official-registryOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.