work_order_get — McpStamp Work Orders MCP Tool
work_order_get
(work order get) is one of 12 tools on the
McpStamp Work Orders
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call work_order_get from your client
- Claude Code McpStamp Work Orders work_order_get run in your project directory
- Claude Desktop McpStamp Work Orders work_order_get ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Work Orders work_order_get ~/.cursor/mcp.json
- VS Code McpStamp Work Orders work_order_get .vscode/mcp.json
- Zed McpStamp Work Orders work_order_get ~/.config/zed/settings.json
- Windsurf McpStamp Work Orders work_order_get ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Work Orders work_order_get ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Work Orders work_order_get ~/.gemini/settings.json
- Grok McpStamp Work Orders work_order_get .mcp.json (in your project root)
- ChatGPT McpStamp Work Orders work_order_get Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Work Orders work_order_get Settings → Connectors → Add custom connector
- LangChain McpStamp Work Orders work_order_get pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http work-order https://mcp.zovo.one/mcp/work-orderOther 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.