mark_invoice_paid — pdf merger MCP Prompt
mark_invoice_paid
is one of 2 prompts on the
pdf merger
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke mark_invoice_paid from your client
- Claude Code pdf merger Prompt/mark_invoice_paid run in your project directory
- Claude Desktop pdf merger Prompt/mark_invoice_paid ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor pdf merger Prompt/mark_invoice_paid ~/.cursor/mcp.json
- VS Code pdf merger Prompt/mark_invoice_paid .vscode/mcp.json
- Zed pdf merger Prompt/mark_invoice_paid ~/.config/zed/settings.json
- Windsurf pdf merger Prompt/mark_invoice_paid ~/.codeium/windsurf/mcp_config.json
- Cline pdf merger Prompt/mark_invoice_paid ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI pdf merger Prompt/mark_invoice_paid ~/.gemini/settings.json
- Grok pdf merger Prompt/mark_invoice_paid .mcp.json (in your project root)
- ChatGPT pdf merger Prompt/mark_invoice_paid Settings → Connectors → Advanced → Developer mode
- Claude.ai pdf merger Prompt/mark_invoice_paid Settings → Connectors → Add custom connector
- LangChain pdf merger Prompt/mark_invoice_paid pip install langchain-mcp-adapters
Other prompts on this server
pdf merger also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.