property-report — PortlandMaps (Unofficial) MCP Prompt

property-report is one of 4 prompts on the PortlandMaps (Unofficial) MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke property-report from your client

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

Other prompts on this server

• show-parcel
• zoning
• code-question

PortlandMaps (Unofficial) 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.