prepare_cutting_paths — Print and Vector QA MCP Tool
prepare_cutting_paths
(prepare cutting paths) is one of 9 tools on the
Print and Vector QA
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_cutting_paths from your client
- Claude Code Print and Vector QA prepare_cutting_paths run in your project directory
- Claude Desktop Print and Vector QA prepare_cutting_paths ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Print and Vector QA prepare_cutting_paths ~/.cursor/mcp.json
- VS Code Print and Vector QA prepare_cutting_paths .vscode/mcp.json
- Zed Print and Vector QA prepare_cutting_paths ~/.config/zed/settings.json
- Windsurf Print and Vector QA prepare_cutting_paths ~/.codeium/windsurf/mcp_config.json
- Cline Print and Vector QA prepare_cutting_paths ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Print and Vector QA prepare_cutting_paths ~/.gemini/settings.json
- Grok Print and Vector QA prepare_cutting_paths .mcp.json (in your project root)
- ChatGPT Print and Vector QA prepare_cutting_paths Settings → Connectors → Advanced → Developer mode
- Claude.ai Print and Vector QA prepare_cutting_paths Settings → Connectors → Add custom connector
- LangChain Print and Vector QA prepare_cutting_paths pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http print-vector-qa https://first-ruble-agent.tohaa28.workers.dev/mcpOther 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.