work_at_height_plan — Ridge Pack MCP Tool
work_at_height_plan
(work at height plan) is one of 8 tools on the
Ridge Pack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call work_at_height_plan from your client
- Claude Code Ridge Pack work_at_height_plan run in your project directory
- Claude Desktop Ridge Pack work_at_height_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ridge Pack work_at_height_plan ~/.cursor/mcp.json
- VS Code Ridge Pack work_at_height_plan .vscode/mcp.json
- Zed Ridge Pack work_at_height_plan ~/.config/zed/settings.json
- Windsurf Ridge Pack work_at_height_plan ~/.codeium/windsurf/mcp_config.json
- Cline Ridge Pack work_at_height_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ridge Pack work_at_height_plan ~/.gemini/settings.json
- Grok Ridge Pack work_at_height_plan .mcp.json (in your project root)
- ChatGPT Ridge Pack work_at_height_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Ridge Pack work_at_height_plan Settings → Connectors → Add custom connector
- LangChain Ridge Pack work_at_height_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ridge-pack https://ridge-pack.nerolabs.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.