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