upgrade_to_pro — bill of sale MCP Prompt

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

bill of sale also offers 1 resource — 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.