Underground Utility Permit Review MCP Server
Related Servers
Alternatives to Underground Utility Permit Review MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables construction permitting teams to analyze portfolios of active permits by ranking risk, detecting day-over-day changes, identifying systemic bottlenecks, and generating daily executive action plans. Also supports single-permit readiness audits, missing-document reports, blocker explanations, resubmission checklists, and semantic search over municipal requirements.71-
- AlicenseAqualityBmaintenanceProvides AI assistants with read-only access to live construction project data and document libraries, enabling issue investigation, schedule risk scoring, and evidence-backed project briefs.6MIT
- FlicenseNot gradedqualityDmaintenanceEnables read-only, natural-language querying of a MySQL permit database, allowing users to ask plain-English questions and receive SQL-backed explanations via Claude Code CLI.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to geotechnical investigation project databases and official standard data interface files from AI workflows, supporting project summaries, borehole lists, arbitrary table queries, and interface file generation, parsing and validation. It also recognizes Excel result tables such as exploration point schedules and dynamic penetration test statistics, converting them into normalized records.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to answer plain-English questions by listing and describing database tables, running read-only SQL queries, and searching a folder of policy documents.MIT
- AlicenseAqualityCmaintenanceProvides Claude Code read-only access to PostgreSQL for relational queries, schema inspection, EXPLAIN plans, pgvector similarity searches, and Apache AGE graph traversals.6Apache 2.0
TDQS
Scored across 5 tools
Each tool addresses a distinct question: per-permit search and retrieval, cross-portfolio risk triage, portfolio-wide summary, and prioritized verification planning. Even search_permits and find_utility_conflicts are clearly separated by intent (query-based vs risk-based scanning).
Four of five tools use a clear verb_noun pattern (search_permits, get_permit, find_utility_conflicts, recommend_verification), but portfolio_summary breaks the pattern by using a noun_noun structure instead of something like summarize_portfolio. This is a minor deviation.
Five tools is ideal for this domain. Each tool has a unique role and the count is not excessive or sparse; the server is well-scoped to the permit review workflow.
The tool surface covers the full read/analysis lifecycle: search (search_permits), detail (get_permit), cross-cutting risk (find_utility_conflicts), roll-up (portfolio_summary), and actionable recommendation (recommend_verification). There are no obvious dead ends or missing operations for the stated purpose.