render_parcel_shape — PortlandMaps (Unofficial) MCP Tool
render_parcel_shape
(render parcel shape) is one of 11 tools on the
PortlandMaps (Unofficial)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call render_parcel_shape from your client
- Claude Code PortlandMaps (Unofficial) render_parcel_shape run in your project directory
- Claude Desktop PortlandMaps (Unofficial) render_parcel_shape ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PortlandMaps (Unofficial) render_parcel_shape ~/.cursor/mcp.json
- VS Code PortlandMaps (Unofficial) render_parcel_shape .vscode/mcp.json
- Zed PortlandMaps (Unofficial) render_parcel_shape ~/.config/zed/settings.json
- Windsurf PortlandMaps (Unofficial) render_parcel_shape ~/.codeium/windsurf/mcp_config.json
- Cline PortlandMaps (Unofficial) render_parcel_shape ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PortlandMaps (Unofficial) render_parcel_shape ~/.gemini/settings.json
- Grok PortlandMaps (Unofficial) render_parcel_shape .mcp.json (in your project root)
- ChatGPT PortlandMaps (Unofficial) render_parcel_shape Settings → Connectors → Advanced → Developer mode
- Claude.ai PortlandMaps (Unofficial) render_parcel_shape Settings → Connectors → Add custom connector
- LangChain PortlandMaps (Unofficial) render_parcel_shape pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http portlandmaps-mcp https://portlandmaps-mcp.vercel.app/mcp/v2Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.