Parcel sources and supported cities — Urban Game Theory — Consensus Builder MCP Resource
Parcel sources and supported cities
is one of 12 resources on the
Urban Game Theory — Consensus Builder
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Parcel sources and supported cities from your client
- Claude Code Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities run in your project directory
- Claude Desktop Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/.cursor/mcp.json
- VS Code Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities .vscode/mcp.json
- Zed Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/.config/zed/settings.json
- Windsurf Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/.codeium/windsurf/mcp_config.json
- Cline Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities ~/.gemini/settings.json
- Grok Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities .mcp.json (in your project root)
- ChatGPT Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities Settings → Connectors → Advanced → Developer mode
- Claude.ai Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities Settings → Connectors → Add custom connector
- LangChain Urban Game Theory — Consensus Builder Resource/Parcel sources and supported cities pip install langchain-mcp-adapters
Other resources on this server
Urban Game Theory — Consensus Builder also offers 5 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 October 2026.
A listing does not declare its resources, 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 resource's type and contents.