Skip to main content
Glama
Underground Utility Permit Review MCP Server

Underground Utility Permit Review MCP Server

by erincheong

Related Servers

Alternatives to Underground Utility Permit Review MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Provides Claude Code read-only access to PostgreSQL for relational queries, schema inspection, EXPLAIN plans, pgvector similarity searches, and Apache AGE graph traversals.
      6
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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).

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.