relocation_brief — Geo-Parity MCP Prompt

relocation_brief is one of 5 prompts on the Geo-Parity MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke relocation_brief from your client

• Claude Code Geo-Parity Prompt/relocation_brief run in your project directory
• Claude Desktop Geo-Parity Prompt/relocation_brief ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Geo-Parity Prompt/relocation_brief ~/.cursor/mcp.json
• VS Code Geo-Parity Prompt/relocation_brief .vscode/mcp.json
• Zed Geo-Parity Prompt/relocation_brief ~/.config/zed/settings.json
• Windsurf Geo-Parity Prompt/relocation_brief ~/.codeium/windsurf/mcp_config.json
• Cline Geo-Parity Prompt/relocation_brief ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Geo-Parity Prompt/relocation_brief ~/.gemini/settings.json
• Grok Geo-Parity Prompt/relocation_brief .mcp.json (in your project root)
• ChatGPT Geo-Parity Prompt/relocation_brief Settings → Connectors → Advanced → Developer mode
• Claude.ai Geo-Parity Prompt/relocation_brief Settings → Connectors → Add custom connector
• LangChain Geo-Parity Prompt/relocation_brief pip install langchain-mcp-adapters

Other prompts on this server

• fair_local_salary
• retire_on_budget
• price_level_provenance
• remote_work_setup

Geo-Parity also offers 4 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.