legislator_accountability — civiq MCP Prompt

legislator_accountability 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 legislator_accountability from your client

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

Other prompts on this server

• bill_impact_analysis
• policy_comparison
• district_deep_dive
• industry_investigation
• 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.