weekly_permit_report — PermitInfoBroker MCP Tool
weekly_permit_report
(weekly permit report) is one of 7 tools on the
PermitInfoBroker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call weekly_permit_report from your client
- Claude Code PermitInfoBroker weekly_permit_report run in your project directory
- Claude Desktop PermitInfoBroker weekly_permit_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PermitInfoBroker weekly_permit_report ~/.cursor/mcp.json
- VS Code PermitInfoBroker weekly_permit_report .vscode/mcp.json
- Zed PermitInfoBroker weekly_permit_report ~/.config/zed/settings.json
- Windsurf PermitInfoBroker weekly_permit_report ~/.codeium/windsurf/mcp_config.json
- Cline PermitInfoBroker weekly_permit_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PermitInfoBroker weekly_permit_report ~/.gemini/settings.json
- Grok PermitInfoBroker weekly_permit_report .mcp.json (in your project root)
- ChatGPT PermitInfoBroker weekly_permit_report Settings → Connectors → Advanced → Developer mode
- Claude.ai PermitInfoBroker weekly_permit_report Settings → Connectors → Add custom connector
- LangChain PermitInfoBroker weekly_permit_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http permits https://permitinfobroker.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 27 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.