upgrade_to_pro — asset register MCP Prompt

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

Other prompts on this server

• depreciate_asset

asset register 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.