OmniData MCP
Related Servers
Alternatives to OmniData MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA Model Context Protocol server that lets LLM clients answer business questions in natural language over a Databricks dataset without writing SQL by hand.1-
- AlicenseAqualityCmaintenanceA read-only DuckDB MCP server offering context-efficient analytics tools (list_datasets, describe_table, profile_column, explain, query) with a semantic layer for business rules, security guards, and disclosed truncation to help LLMs produce correct answers while minimizing token usage.5MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation that connects AI assistants to DuckDB, enabling them to query and analyze data from various sources including CSV, Parquet, JSON, and cloud storage through SQL.18MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables large language models to access database metadata and perform cross-engine data querying across diverse database ecosystems.1653Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn enhanced Model Context Protocol server that enables LLMs to inspect database schemas with rich metadata and execute read-only SQL queries with safety checks.90 npm25MIT
- FlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.-
TDQS
Scored across 8 tools
Each tool targets a distinct concern: health check, dataset discovery, schema introspection, row counting, SQL queries, profiling, charting, and declarative transformations. Even run_sql_query vs generate_chart are clearly differentiated by output type (structured data vs. image).
The naming convention is predominantly verb_noun (list_datasets, get_schema, run_sql_query, generate_chart, execute_pyspark_job). The sole outlier is health_check, which follows noun_verb order and is not consistent with the others.
With 8 tools, the server is well-scoped for a database analytics MCP. Each tool covers a genuine need without redundancy or bloat, staying within the ideal 3-15 range.
The tool surface covers the full analytical lifecycle: connect/health, explore structure, query, profile, chart, and transform. While data modification is intentionally absent, all read-only analysis needs are addressed without obvious gaps.