industry_investigation — civiq MCP Prompt

industry_investigation is one of 6 prompts on the civiq MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke industry_investigation from your client

• Claude Code civiq Prompt/industry_investigation run in your project directory
• Claude Desktop civiq Prompt/industry_investigation ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor civiq Prompt/industry_investigation ~/.cursor/mcp.json
• VS Code civiq Prompt/industry_investigation .vscode/mcp.json
• Zed civiq Prompt/industry_investigation ~/.config/zed/settings.json
• Windsurf civiq Prompt/industry_investigation ~/.codeium/windsurf/mcp_config.json
• Cline civiq Prompt/industry_investigation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI civiq Prompt/industry_investigation ~/.gemini/settings.json
• Grok civiq Prompt/industry_investigation .mcp.json (in your project root)
• ChatGPT civiq Prompt/industry_investigation Settings → Connectors → Advanced → Developer mode
• Claude.ai civiq Prompt/industry_investigation Settings → Connectors → Add custom connector
• LangChain civiq Prompt/industry_investigation pip install langchain-mcp-adapters

Other prompts on this server

• legislator_accountability
• bill_impact_analysis
• policy_comparison
• district_deep_dive
• environmental_justice

civiq also offers 3 resources — 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 24 September 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.