fgis-mcp
Related Servers
Alternatives to fgis-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables 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- FlicenseAqualityDmaintenanceEnables AI clients to search and read Korean Construction Standards (KCS/KDS) documents directly, using the KCSC OpenAPI.42-
- AlicenseAqualityCmaintenanceMCP server that exposes the version history of Russian construction-pricing open data (ФГИС ЦС), enabling queries about dataset versions, salary changes, and republished-but-unchanged exports.41MIT
- AlicenseAqualityBmaintenanceOffline MCP server for querying Russian construction normative rates (FSNB-2022/GESN) via SQLite with full-text search.510 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to search, fetch, and apply portable engineering standards over MCP, keyless and offline.4MIT
- AlicenseAqualityAmaintenanceA remote MCP server for Korean AEC standards (KDS, KCS, KS, building law) that answers with exact clause numbers and confidence scores, and refuses to guess when no grounds are found. It also preserves privacy by never storing query text on disk.12Apache 2.0
TDQS
Scored across 19 tools
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.
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.
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.
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.