Property Condition Defects Catalog — GISDB MCP Resource
Property Condition Defects Catalog
is one of 6 resources on the
GISDB
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Property Condition Defects Catalog from your client
- Claude Code GISDB Resource/Property Condition Defects Catalog run in your project directory
- Claude Desktop GISDB Resource/Property Condition Defects Catalog ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GISDB Resource/Property Condition Defects Catalog ~/.cursor/mcp.json
- VS Code GISDB Resource/Property Condition Defects Catalog .vscode/mcp.json
- Zed GISDB Resource/Property Condition Defects Catalog ~/.config/zed/settings.json
- Windsurf GISDB Resource/Property Condition Defects Catalog ~/.codeium/windsurf/mcp_config.json
- Cline GISDB Resource/Property Condition Defects Catalog ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GISDB Resource/Property Condition Defects Catalog ~/.gemini/settings.json
- Grok GISDB Resource/Property Condition Defects Catalog .mcp.json (in your project root)
- ChatGPT GISDB Resource/Property Condition Defects Catalog Settings → Connectors → Advanced → Developer mode
- Claude.ai GISDB Resource/Property Condition Defects Catalog Settings → Connectors → Add custom connector
- LangChain GISDB Resource/Property Condition Defects Catalog pip install langchain-mcp-adapters
Other resources on this server
GISDB 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 14 November 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.