Claude MCP Data Explorer
Related Servers
Alternatives to Claude MCP Data Explorer
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that analyzes customer cancellation survey data, enabling Claude AI integration through HTTP/SSE transport.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for exploring and analyzing CSV files, providing tools for inspection, sampling, schema inference, statistics, filtering, and more.121 npmMIT
- AlicenseAqualityNot gradedmaintenanceAn MCP server that enables AI assistants to load, query, and analyze local CSV files using tools for filtering, aggregation, and grouping. It provides capabilities to describe schemas, calculate statistics, and sample data directly from CSV files.6-
- FlicenseNot gradedqualityDmaintenanceA local MCP server for analyzing CSV files from your filesystem, particularly suited for chatbot conversation logs. Allows listing, reading, filtering, merging, and statistical analysis of CSV data via natural language.-
- FlicenseAqualityDmaintenanceAn MCP server for dataset exploration and analysis, enabling LLM clients to perform summary, correlation, distribution, missing value analysis, data cleaning, and statistical tests directly on CSV files.3-
- FlicenseBqualityCmaintenanceEnables AI assistants to load CSV datasets, compute summary statistics, filter rows, rank columns, and compute correlations through the Model Context Protocol.6-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one loads CSV data into a DataFrame, while the other executes JavaScript scripts for analysis and visualization. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools use a verb-noun pattern (load-csv, run-script), which is consistent and readable. The hyphenated style is maintained throughout, though the specific convention (hyphens vs. underscores) is less important than the consistency, which is good here with only minor deviations from common patterns.
With only two tools, the server feels thin for a 'Data Explorer' purpose, as it lacks essential operations like data querying, filtering, transformation, or exporting. While the tools are functional, the count is too low to adequately cover the expected scope of data exploration and analysis.
For a data exploration server, there are significant gaps: no tools for querying data, filtering, aggregating, visualizing beyond scripts, or exporting results. The surface is severely incomplete, as agents cannot perform basic data exploration tasks without relying heavily on external scripts, leading to potential failures in common workflows.