Zaturn
Related Servers
Alternatives to Zaturn
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for SQL analytics on DuckDB and MotherDuck databases, enabling AI assistants and IDEs to query data via natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server enabling AI assistants to query and analyze data via DuckDB SQL engine, supporting local files, memory, S3, and MotherDuck.16Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP (Model Context Protocol) server that exposes natural language to SQL functionality, allowing any MCP-compatible client to convert plain English questions into SQL queries for database interaction using AI.3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables SQL analytics on DuckDB and MotherDuck databases, allowing AI assistants and IDEs to query and analyze data.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for Apache Superset that enables AI models to manage dashboards, create charts with auto-detection, and execute SQL queries programmatically. It utilizes stateless HTTP transport to ensure compatibility with integration tools like Open WebUI.153MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that exposes relational databases (PostgreSQL/MySQL) to AI agents with natural language to SQL query support.19-
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose: 10 visualization tools each create different plot types (bar, box, scatter, etc.), 'run_query' returns raw data, 'list_data_sources' enumerates sources, and 'describe_table' provides schema information. There is no functional overlap between tools - an agent can easily select the right tool for each task.
All tools follow a consistent snake_case naming convention with clear verb_noun patterns: visualization tools use plot_type names (bar_plot, scatter_plot), while utility tools use action_object patterns (run_query, list_data_sources, describe_table). The naming is perfectly predictable and follows a single convention throughout.
12 tools is well-scoped for a data visualization and query server. The count includes comprehensive visualization coverage (10 plot types), core data operations (run_query), and metadata utilities (list_data_sources, describe_table). Each tool earns its place without redundancy or bloat.
The toolset provides excellent coverage for data exploration and visualization: query execution, schema inspection, source enumeration, and multiple plot types. Minor gaps include lack of data modification tools (update/delete) and advanced analytics functions, but these may be outside the server's intended scope as a visualization-focused tool.