upgrade_to_pro — pdf split merge compress MCP Prompt

upgrade_to_pro is one of 2 prompts on the pdf split merge compress MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke upgrade_to_pro from your client

• Claude Code pdf split merge compress Prompt/upgrade_to_pro run in your project directory
• Claude Desktop pdf split merge compress Prompt/upgrade_to_pro ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor pdf split merge compress Prompt/upgrade_to_pro ~/.cursor/mcp.json
• VS Code pdf split merge compress Prompt/upgrade_to_pro .vscode/mcp.json
• Zed pdf split merge compress Prompt/upgrade_to_pro ~/.config/zed/settings.json
• Windsurf pdf split merge compress Prompt/upgrade_to_pro ~/.codeium/windsurf/mcp_config.json
• Cline pdf split merge compress Prompt/upgrade_to_pro ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI pdf split merge compress Prompt/upgrade_to_pro ~/.gemini/settings.json
• Grok pdf split merge compress Prompt/upgrade_to_pro .mcp.json (in your project root)
• ChatGPT pdf split merge compress Prompt/upgrade_to_pro Settings → Connectors → Advanced → Developer mode
• Claude.ai pdf split merge compress Prompt/upgrade_to_pro Settings → Connectors → Add custom connector
• LangChain pdf split merge compress Prompt/upgrade_to_pro pip install langchain-mcp-adapters

Other prompts on this server

• mark_invoice_paid

pdf split merge compress 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 26 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.