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