Skip to main content
Glama

Related Servers

Alternatives to fgis-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and manage construction project economic data, including unit price analyses, resource catalogs, budget trees, and price lists, with secure multi-tenant access.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes the version history of Russian construction-pricing open data (ФГИС ЦС), enabling queries about dataset versions, salary changes, and republished-but-unchanged exports.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to query construction management companies, projects, and directory data, and to create safety-gated draft records without permitting terminal commitments. It also provides credential resolution, context compression, audit logging, mock/demo sandbox modes, and remote transports for enterprise deployments.
      Business Source 1.1
    • 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.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Offline MCP server for querying Russian construction normative rates (FSNB-2022/GESN) via SQLite with full-text search.
      5
      8 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target distinct resources and actions: source/catalog browsing, norm search vs read, online vs dataset reads, and job lifecycle tools are clearly separated. Some potential confusion exists between fgis_sources, fgis_catalog, and fgis_browse_source, and between offline query_dataset and online search_norms/search_document, but the descriptions are specific enough to disambiguate.

    Naming Consistency4/5

    All tools share the fgis_ prefix and most follow a verb_noun pattern such as search_norms, read_document, cancel_job, and export_dataset. A few noun-style names like fgis_sources, fgis_catalog, fgis_dataset_info, and fgis_job_status, plus verb-only fgis_diagnose, break the pattern slightly, but the convention is still readable and predictable.

    Tool Count3/5

    19 tools is on the heavy side and sits in the borderline range for a single MCP server. The tools are largely distinct, but catalog/source browsing, document reading, and job management could potentially be consolidated without losing much clarity.

    Completeness4/5

    The surface covers the full read-oriented workflow: discover sources and catalogues, browse and search online, start and manage downloads, then query, read, and export saved datasets. Minor gaps such as no direct way to fetch a dataset by ID from a job result and no dataset deletion/pruning keep it from a perfect score, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues