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