huggingface/hf-mcp-server

Welcome to the official Hugging Face MCP Server 🤗. Connect your LLM to the Hugging Face Hub and thousands of Gradio AI Applications.
## Installing the MCP Server
Follow the instructions below to get started:
Install in Claude Desktop or claude.ai
Click here to add the Hugging Face connector to your account.
Alternatively, navigate to https://claude.ai/settings/connectors, and add "Hugging Face" from the gallery.
Install in Claude Code
Enter the command below to install in Claude Code :
bash
claude mcp add hf-mcp-server -t http https://huggingface.co/mcp?login
Then start claude and follow the instructions to complete authentication.
bash
claude mcp add hf-mcp-server \
-t http https://huggingface.co/mcp \
-H "Authorization: Bearer "
Install in Gemini CLI
Enter the command below to install in Gemini CLI :
bash
gemini mcp add -t http huggingface https://huggingface.co/mcp?login
Then start gemini and follow the instructions to complete authentication.
Install in VSCode
Click here to add the Hugging Face connector directly to VSCode. Alternatively, install from the gallery at https://code.visualstudio.com/mcp:
If you prefer to configure manually or use an auth token, add the snippet below to your mcp.json configuration:
JSON
"huggingface": {
"url": "https://huggingface.co/mcp",
"headers": {
"Authorization": "Bearer "
Install in Cursor
Click here to install the Hugging Face MCP Server directly in Cursor .
If you prefer to use configure manually or specify an Authorization Token, use the snippet below:
JSON
"huggingface": {
"url": "https://huggingface.co/mcp",
"headers": {
"Authorization": "Bearer "
Once installed, navigate to https://huggingface.co/settings/mcp to configure your Tools and Spaces.
> [!TIP]
> Add ?noimagecontent=true to the URL to remove ImageContent blocks from Gradio Servers.
## Quick Guide (Repository Packages)
This repo contains:
(/mcp) MCP Implementations of Hub API and Search endpoints for integration with MCP Servers.
(/app) An MCP Server and Web Application for deploying endpoints.
### MCP Server
The following transports are supported:
STDIO
StreamableHTTP in Stateless JSON Mode (StreamableHTTPJson)
The Web Application and HTTP Transports start by default on Port 3000.
The StreamableHTTP service is available at /mcp. Although not strictly enforced by the specification, this is a common convention.
The public Streamable HTTP deployment serves its MCP Server Card at /mcp/server-card. The public card advertises the canonical https://huggingface.co/mcp endpoint without authentication-specific query parameters; loopback deployments and explicit non-Hugging Face hosts in MCPALLOWEDHOSTS advertise their own /mcp endpoint. Card responses support cache revalidation with an ETag.
The Web Application at /metrics reports server status and MCP method metrics.
The Skills tab shows process-local catalog health and live Skills activity, filtered by time window (15m/1h/24h), client name/version, method, and outcome. It separates metadata probes (skills/list, skills/get, directory reads) from successful SKILL.md and supporting-file content reads; retrieval does not prove execution or complete installation. Client names/versions are self-reported. Activity is capped at 10,000 events and 24 hours, resets on restart, and flags incomplete coverage. It is independent of LOGSKILLEVENTS; historical events remain in the configured dataset's skills/YYYY-MM-DD/ logs. Live activity currently covers the streamableHttpJson transport. Health polling never loads/refreshes the catalog and explicitly warns that manifest byte-size verification is not yet implemented. Skills dashboard telemetry contains no target URIs, user hashes, session IDs, or file contents.