Hugging Face MCP Server
Related Servers
Alternatives to Hugging Face MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables access to the Hugging Face Hub API to search and retrieve information about machine learning models, datasets, and their metadata. Provides comprehensive tools for exploring the Hugging Face ecosystem including model details, dataset information, and parquet file access.8-
- AlicenseNot gradedqualityDmaintenanceProvides direct access to the Hugging Face Hub for searching models and datasets, fetching metadata, and running inference on text, images, and audio.MIT
- AlicenseNot gradedqualityBmaintenanceSearch and retrieve models, datasets, and spaces from Hugging Face Hub. Enables browsing trending items and getting detailed info on repos.13 npmMIT
- AlicenseAqualityAmaintenanceEnables assistants to search, fetch daily curated lists, retrieve metadata, and generate citations for Hugging Face papers.619 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables searching, fetching, and analyzing scientific papers from ArXiv, ACL Anthology, Semantic Scholar, and Hugging Face datasets, with optional LLM-powered document QA and research proposal workflows.92Apache 2.0
- AlicenseBqualityDmaintenanceEnables interaction with the Hugging Face Dataset Viewer API, allowing users to browse, search, filter, and analyze datasets hosted on the Hugging Face Hub.831MIT
TDQS
Scored across 10 tools
Each resource type (models, datasets, spaces, papers, collections) has a clear search/get pair, so boundaries are generally distinct. The only mild overlap is between get-daily-papers (a curated list) and get-paper-info (a specific paper), but the descriptions distinguish them adequately.
All names follow a hyphenated verb-first pattern (search-X, get-X-info), which is predictable and readable. Minor inconsistency: search tools use plural resource nouns (search-models) while get tools use singular (get-model-info), plus get-daily-papers deviates slightly in structure.
Ten tools is well within the ideal 3-15 range and each is scoped to a distinct resource/action. No redundant or filler tools; the set maps cleanly onto the Hub's main entity types.
Strong coverage of the read/lookup lifecycle across models, datasets, spaces, papers, and collections, covering the hub-browsing domain well. Minor gaps: no general paper search (only curated daily papers) and no file/tree listing or author/org tools, but these are workaround-able.