research_a_property — MarketCode MCP Prompt
research_a_property
is one of 4 prompts on the
MarketCode
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke research_a_property from your client
- Claude Code MarketCode Prompt/research_a_property run in your project directory
- Claude Desktop MarketCode Prompt/research_a_property ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MarketCode Prompt/research_a_property ~/.cursor/mcp.json
- VS Code MarketCode Prompt/research_a_property .vscode/mcp.json
- Zed MarketCode Prompt/research_a_property ~/.config/zed/settings.json
- Windsurf MarketCode Prompt/research_a_property ~/.codeium/windsurf/mcp_config.json
- Cline MarketCode Prompt/research_a_property ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MarketCode Prompt/research_a_property ~/.gemini/settings.json
- Grok MarketCode Prompt/research_a_property .mcp.json (in your project root)
- ChatGPT MarketCode Prompt/research_a_property Settings → Connectors → Advanced → Developer mode
- Claude.ai MarketCode Prompt/research_a_property Settings → Connectors → Add custom connector
- LangChain MarketCode Prompt/research_a_property pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 14 November 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.