get_permit_details — PermitSnag MCP Tool Read-only
get_permit_details
(get permit details) is one of 6 tools on the
PermitSnag
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_permit_details from your client
- Claude Code PermitSnag get_permit_details run in your project directory
- Claude Desktop PermitSnag get_permit_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PermitSnag get_permit_details ~/.cursor/mcp.json
- VS Code PermitSnag get_permit_details .vscode/mcp.json
- Zed PermitSnag get_permit_details ~/.config/zed/settings.json
- Windsurf PermitSnag get_permit_details ~/.codeium/windsurf/mcp_config.json
- Cline PermitSnag get_permit_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PermitSnag get_permit_details ~/.gemini/settings.json
- Grok PermitSnag get_permit_details .mcp.json (in your project root)
- ChatGPT PermitSnag get_permit_details Settings → Connectors → Advanced → Developer mode
- Claude.ai PermitSnag get_permit_details Settings → Connectors → Add custom connector
- LangChain PermitSnag get_permit_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http permits https://api.permitsnag.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 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.