upgrade_to_pro — per diem MCP Prompt

upgrade_to_pro is one of 2 prompts on the per diem 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 per diem Prompt/upgrade_to_pro run in your project directory
• Claude Desktop per diem Prompt/upgrade_to_pro ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor per diem Prompt/upgrade_to_pro ~/.cursor/mcp.json
• VS Code per diem Prompt/upgrade_to_pro .vscode/mcp.json
• Zed per diem Prompt/upgrade_to_pro ~/.config/zed/settings.json
• Windsurf per diem Prompt/upgrade_to_pro ~/.codeium/windsurf/mcp_config.json
• Cline per diem Prompt/upgrade_to_pro ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI per diem Prompt/upgrade_to_pro ~/.gemini/settings.json
• Grok per diem Prompt/upgrade_to_pro .mcp.json (in your project root)
• ChatGPT per diem Prompt/upgrade_to_pro Settings → Connectors → Advanced → Developer mode
• Claude.ai per diem Prompt/upgrade_to_pro Settings → Connectors → Add custom connector
• LangChain per diem Prompt/upgrade_to_pro pip install langchain-mcp-adapters

Other prompts on this server

• claim_trip

per diem 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.