upgrade_to_pro — service contract MCP Prompt

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

service contract 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.