HF Dataset MCP
Related Servers
Alternatives to HF Dataset MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn unofficial MCP server that provides semantic search capabilities for Hugging Face models and datasets, enabling Claude and other MCP-compatible clients to search, discover, and explore the Hugging Face ecosystem using natural language queries.20MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that searches HuggingFace/Kaggle for datasets, detects their domain, and generates a matching preprocessing script. It turns natural-language dataset queries into runnable, domain-aware preprocessing pipelines.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides Hugging Face Hub API and Search endpoints through multiple transport protocols (STDIO, SSE, StreamableHTTP, and StreamableHTTPJson), enabling integration with AI model capabilities.293MIT
- AlicenseNot gradedqualityDmaintenanceUnified MCP server for discovering open datasets across Hugging Face, Zenodo, and Kaggle, with ranked search results and one-click Colab starter code generation.1MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server provides a local-first Text2SQL assistant for Discord, allowing users to query BIRD Mini-Dev SQL databases through natural language. It exposes tools for dataset search, schema retrieval, and safe read-only SQL execution.MIT
- AlicenseAqualityDmaintenanceThis MCP server enables users to interact with and analyze the dair-ai/emotion dataset from Hugging Face containing labeled Twitter messages. It provides tools to sample data, search text, and perform statistical analysis on emotion distributions.4GPL 3.0
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose with no overlap: filtering rows, getting metadata, fetching rows, searching datasets, etc. The descriptions clearly differentiate operations like get_rows vs. filter_rows vs. search_dataset, preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case (e.g., filter_rows, get_dataset_info, list_splits). The naming is predictable and readable throughout the set, with no deviations in style.
With 10 tools, this is well-scoped for a dataset management server. Each tool serves a specific function in exploring, querying, and validating datasets, with no redundant or missing tools that would make the set feel too thin or bloated.
The toolset provides complete coverage for dataset operations: discovery (search_datasets, list_splits), inspection (get_dataset_info, get_statistics), access (get_rows, list_parquet_files), querying (filter_rows, search_dataset), and validation (validate_dataset). No obvious gaps exist for the domain.