get_violation — PermitStack MCP Tool Read-only
get_violation
(get violation) is one of 18 tools on the
PermitStack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_violation from your client
- Claude Code PermitStack get_violation run in your project directory
- Claude Desktop PermitStack get_violation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PermitStack get_violation ~/.cursor/mcp.json
- VS Code PermitStack get_violation .vscode/mcp.json
- Zed PermitStack get_violation ~/.config/zed/settings.json
- Windsurf PermitStack get_violation ~/.codeium/windsurf/mcp_config.json
- Cline PermitStack get_violation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PermitStack get_violation ~/.gemini/settings.json
- Grok PermitStack get_violation .mcp.json (in your project root)
- ChatGPT PermitStack get_violation Settings → Connectors → Advanced → Developer mode
- Claude.ai PermitStack get_violation Settings → Connectors → Add custom connector
- LangChain PermitStack get_violation pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http permits https://mcp.permit-stack.com/mcpOther tools on this server
- search_permits
- get_permit
- get_property_history
- search_contractors
- get_contractor_permits
- get_coverage
- search_inspections
- get_permit_inspections
- search_violations
- search_pipeline_cases
- get_pipeline_case
- search_pipeline_decisions
- search_certificates
- get_certificate
- lookup_license
- get_contractor_licenses
- get_dataset_coverage
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.