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