Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.
Hugging FaceMCP Server
Summary
Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.
Features
- Remote streamable-HTTP endpoint at huggingface.co/mcp, with OAuth via ?login or a Bearer token
- Hub repository search and detail across models, datasets and Spaces
- hf_fs reads repository files without cloning
- Exposes Gradio Spaces as callable tools — thousands of community apps as tool calls
- Per-account tool and Space selection at huggingface.co/settings/mcp
- Self-hostable over STDIO or HTTP via npm or the ghcr.io container, with a /metrics dashboard
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
This is Hugging Face's official MCP server, connecting an agent to the Hugging Face Hub and to the Gradio applications hosted on it. It runs remotely at https://huggingface.co/mcp over stateless streamable HTTP, and the same code can be run locally over STDIO.
What it reaches
The built-in tools cover Hub search and metadata — repository search and repository detail across models, datasets and Spaces — plus hf_fs, a filesystem-style tool for reading repository contents without cloning. Beyond the static set, the server can expose Gradio Spaces as callable tools, which is the part that makes it unusual: an agent gains access to thousands of community-built demos (image generation, transcription, classification) as ordinary tool calls rather than as web pages to drive.
A ?bouquet= query parameter selects which group of tools is advertised. ?bouquet=openai exposes the Hub filesystem, repository search and detail, dynamic Space, Jobs and sandbox tools; the Jobs, dynamic Space and sandbox tools require authentication. Which tools and Spaces a given account sees is configured at huggingface.co/settings/mcp, and ?no_image_content=true strips ImageContent blocks from Gradio responses for clients that cannot render them.
Authentication
Adding ?login to the endpoint runs an OAuth flow; alternatively a Hugging Face token can be sent in an Authorization: Bearer header. Anonymous use works for public read operations, while Jobs and sandbox tools require a token.
Running it yourself
The server is published on npm as @llmindset/hf-mcp-server (STDIO) and @llmindset/hf-mcp-server-http (stateless streamable HTTP JSON), and as a container at ghcr.io/evalstate/hf-mcp-server. Self-hosted deployments get a management interface at /metrics reporting server status and per-method metrics, an allowlist via MCP_ALLOWED_HOSTS, and a DISABLE_TOOLS list for hiding individual tools such as hub_repo_search or hf_fs.
The project is MIT-licensed and developed in the open at huggingface/hf-mcp-server.
Related MCP Servers
Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.
Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.
Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.