gx-mcp-server
Related Servers
Alternatives to gx-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceExposes the automated feature engineering LangGraph agent as MCP tools, enabling dataset profiling, feature planning, and feature code execution through MCP-compatible hosts.-
- FlicenseNot gradedqualityBmaintenanceExposes schema, lineage, and data-quality trust signals from a SQLite-backed catalog as MCP tools, enabling AI agents to answer grounded questions about datasets without hallucinating.-
- AlicenseNot gradedqualityBmaintenanceExposes Iceberg-backed ontology objects, links, and actions as typed MCP tools for LLM agents, enabling governed data access and operations without raw SQL.MIT
- AlicenseBqualityBmaintenanceExposes data query and auto-insights (anomaly detection) as MCP tools. Enables AI agents to query metrics, list columns, and get data insights directly from pandas.11MIT
- FlicenseNot gradedqualityDmaintenanceExposes task management (add, list, complete tasks) and document search (RAG) as MCP tools for AI agents.-
- FlicenseAqualityDmaintenanceExposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.2-
TDQS
Scored across 7 tools
Each tool addresses a distinct concern: health/version, data loading, suite/expectation management, and validation execution/result retrieval. There is no overlap between run_checkpoint and get_validation_result, as one performs the validation and the other retrieves its output.
All tools follow a snake_case verb_noun pattern (run_checkpoint, get_validation_result, load_dataset, create_suite, add_expectation, get_version), with 'ping' as the only exception but it is a standard health-check name. The convention is uniform and predictable.
Seven tools is well within the ideal range for a focused MCP server. Each tool serves a necessary function for the core workflow of building and running data validation, with no redundancy or scope creep.
The set covers the primary workflow (load data, create suite, add expectation, run checkpoint, get result), but lacks read operations for existing suites or expectations, and has no update/delete capabilities. Agents cannot discover or manage existing validation assets without extending the surface.