dts-mcp-server
Related Servers
Alternatives to dts-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceMCP server for the Geopera geospatial data platform that enables AI agents to discover imagery, place and manage orders, and run analytics using the same API as other Geopera clients.100MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for inspecting, analysing, and editing CityJSON and CityGML building datasets.-
- FlicenseNot gradedqualityDmaintenanceMCP server providing tools for spatial grid applications including calculations, MongoDB management, asset management, project creation, and experience publishing.-
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that brings AI-powered automation to Agisoft Metashape Professional. Enables natural language control of photogrammetry tasks such as drone mapping, 3D model generation, and export.34MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-driven CAD operations, enabling parametric modeling, build, inspection, measurement, rendering, and diff comparison with STEP, DXF, and GLB export.MIT
- FlicenseAqualityCmaintenanceMCP server for the BAIC Data Layer. Provides tools to manage sources, knowledge bases, knowledge clusters, run data agents, and create/manage pipelines.36-
TDQS
Scored across 8 tools
Each tool targets a distinct operation: health check, pipeline enumeration, error lookup, validation, job type enumeration, standard publish, OSGB publish, and job file creation. The two publish tools are clearly separated by data format, so no ambiguity exists.
All tools share the dts_ prefix and use snake_case with a consistent verb_noun pattern (e.g., dts_list_pipelines, dts_explain_error, dts_create_job). The one exception, dts_publish_osgb, still follows the pattern with a format suffix and remains predictable.
With 8 tools, the server is well-scoped for its domain. Each tool serves a necessary role in the DTS Engine workflow without redundancy or excessive granularity.
The tool set covers the full operational lifecycle: checking engine health, listing pipelines and job types, validating flags, running both standard and OSGB publishes, creating job files, and explaining errors. No obvious gaps exist for the stated purpose.