Hugging Face MCP Server Details

Hugging Face Official MCP Server connects your large language models (LLMs) to the Hugging Face Hub and thousands of Gradio AI Applications, enabling seamless MCP (Model Context Protocol) integration across multiple transports. It supports STDIO, SSE (to be deprecated but still commonly deployed), StreamableHTTP, and StreamableHTTPJson, with the Web Application allowing dynamic tool management and status updates. This MCP server is designed to be run locally or in Docker, and it provides integrations with Claude Desktop, Claude Code, Gemini CLI (and its extension), VSCode, and Cursor, making it easy to configure and manage MCP-enabled tools and endpoints. Tools such as hf_doc_search and hf_doc_fetch can be enabled to enhance document discovery, and an optional Authenticate tool can be included to handle OAuth challenges when called.

Use Case

The MCP Server acts as a bridge between LLM clients and MCP-enabled endpoints, orchestrating tool availability and communication across multiple transports. It is capable of running in STDIO, SSE, Streamable HTTP, or JSON-mode HTTP, allowing flexible deployments from local development to production-grade configurations. The Web UI lets you switch tools on and off, and the server can automatically enable document-related tools when document search is enabled. Example deployment patterns include installing via Claude or Gemini CLI, or integrating with VSCode or Cursor for seamless tooling within development environments.

Key usage patterns from the documentation include:

  • Running locally with npx to start in different modes:
  • npx @llmindset/hf-mcp-server       # Start in STDIO mode
    npx @llmindset/hf-mcp-server-http # Start in Streamable HTTP mode
    npx @llmindset/hf-mcp-server-json # Start in Streamable HTTP (JSON RPC) mode

  • Running with Docker:
  • docker pull ghcr.io/evalstate/hf-mcp-server:latest
    docker run --rm -p 3000:3000 ghcr.io/evalstate/hf-mcp-server:latest

  • Installing in Claude Desktop / Claude Code / Gemini CLI / VSCode / Cursor, with example commands:
  • claude mcp add hf-mcp-server -t http https://huggingface.co/mcp?login

    claude mcp add hf-mcp-server \
    -t http https://huggingface.co/mcp \
    -H "Authorization: Bearer <YOUR_HF_TOKEN>"

    gemini mcp add -t http huggingface https://huggingface.co/mcp?login

    gemini extensions install https://github.com/huggingface/hf-mcp-server

    To configure VSCode manually, the example mcp.json snippet is shown as:

    "huggingface": {
    "url": "https://huggingface.co/mcp",
    "headers": {
    "Authorization": "Bearer <YOUR_HF_TOKEN>"
    }

    Similarly, Cursor users can install via a provided link and use a config snippet like:

    "huggingface": {
    "url": "https://huggingface.co/mcp",
    "headers": {
    "Authorization": "Bearer <YOUR_HF_TOKEN>"
    }

    Available Tools (3)

    Examples & Tutorials

    Real examples and usage patterns directly from the docs:

  • Install and connect via Claude Desktop / Claude Code:
  • claude mcp add hf-mcp-server -t http https://huggingface.co/mcp?login

    claude mcp add hf-mcp-server \
    -t http https://huggingface.co/mcp \
    -H "Authorization: Bearer <YOUR_HF_TOKEN>"

  • Install via Gemini CLI:
  • gemini mcp add -t http huggingface https://huggingface.co/mcp?login

  • Install the Gemini CLI extension that bundles the MCP server:
  • gemini extensions install https://github.com/huggingface/hf-mcp-server

  • VSCode integration snippet (mcp.json):
  • "huggingface": {
    "url": "https://huggingface.co/mcp",
    "headers": {
    "Authorization": "Bearer <YOUR_HF_TOKEN>"
    }

  • Cursor integration snippet (mcp.json):
  • "huggingface": {
    "url": "https://huggingface.co/mcp",
    "headers": {
    "Authorization": "Bearer <YOUR_HF_TOKEN>"
    }

  • Run locally in different modes:
  • npx @llmindset/hf-mcp-server       # Start in STDIO mode
    npx @llmindset/hf-mcp-server-http # Start in Streamable HTTP mode
    npx @llmindset/hf-mcp-server-json # Start in Streamable HTTP (JSON RPC) mode

  • Docker-based run:
  • docker build -t hf-mcp-server .

    docker run --rm -p 3000:3000 -e DEFAULT_HF_TOKEN=hf_xxx hf-mcp-server

    Installation Guide

    Follow these steps from the documentation to install and run the MCP Server:

  • Install and run locally with npx (choose mode):
  • npx @llmindset/hf-mcp-server       # Start in STDIO mode
    npx @llmindset/hf-mcp-server-http # Start in Streamable HTTP mode
    npx @llmindset/hf-mcp-server-json # Start in Streamable HTTP (JSON RPC) mode

  • Run with Docker:
  • docker pull ghcr.io/evalstate/hf-mcp-server:latest
    docker run --rm -p 3000:3000 ghcr.io/evalstate/hf-mcp-server:latest

    docker build -t hf-mcp-server .

    docker run --rm -p 3000:3000 -e DEFAULT_HF_TOKEN=hf_xxx hf-mcp-server

  • Transport endpoints overview:

  • STDIO uses stdin/stdout; SSE is available at /sse with /message endpoint; Streamable HTTP at /mcp (JSON mode when using streamableHttpJson).

  • Integration Guides

    Frequently Asked Questions

    Is this your MCP?

    Claim ownership and get verified badge

    Repository Stats

    Sponsored

    Ad Space Available
    Important Notes

    SSE is marked as To be deprecated, but it is still commonly deployed. The Web Application can switch tools on and off, and in certain transports (STDIO, SSE, StreamableHTTP) the ToolListChangedNotification is sent when tools change. In JSON mode for StreamableHTTPJSON, a tool may not be listed when the client requests tool lists. Environment variables include MCP_STRICT_COMPLIANCE (GET 405 rejects in JSON mode) and AUTHENTICATE_TOOL (whether to include an Authenticate tool).

    Prerequisites

    pnpm is used for build and development; Corepack is used to ensure everyone uses the same pnpm version (10.12.3).

    Details
    Last Updated1/2/2026
    SourceGitHub

    Compare Alternatives

    Similar MCP Tools

    9 related tools
    Playwright MCP

    Playwright MCP

    Playwright MCP server. A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. The server is designed to be fast, lightweight, and deterministic, offering LLM-friendly tooling and a rich set of browser automation capabilities via MCP tools. It supports standalone operation, containerized deployments, and integration with a variety of MCP clients (Claude Desktop, VS Code, Copilot, Cursor, Goose, Windsurf, and others).

    Sequential Thinking MCP Server

    Sequential Thinking MCP Server

    Sequential Thinking MCP Server provides a dedicated MCP tool that guides problem-solving through a structured, step-by-step thinking process. It supports dynamic adjustment of the number of thoughts and allows revision and branching within a controlled workflow, making it ideal for complex analysis and solution hypothesis development. This server is designed to register a single tool, sequential_thinking, and is integrated with common MCP deployment methods (NPX, Docker) as well as editor integrations like Claude Desktop and VS Code for quick setup. The documentation provides exact configuration snippets, usage patterns, and building instructions to help you deploy and use the MCP server effectively, including Codex CLI, NPX, and Docker installation examples.

    N8N MCP Server

    N8N MCP Server

    An MCP (Model Context Protocol) server designed to integrate Claude Desktop, Claude Code, Windsurf, and Cursor with n8n workflows. This MCP enables users to build, test, and orchestrate complex workflows by exposing a set of tools that bridge Claude’s capabilities with n8n’s automation platform. The project emphasizes robust trigger handling, multi-tenant readiness, and progressive documentation to help developers understand how tools map to real-world workflow tasks. It also outlines future tooling integration points (such as getNodeEssentials and getNodeInfo) to further enhance node-structure awareness within MCP-powered automations.

    Shadcn UI MCP Server v4

    Shadcn UI MCP Server v4

    Shadcn UI v4 MCP Server is an advanced MCP (Model Context Protocol) server designed to give AI assistants comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata. It enables multi-framework support (React, Svelte, Vue, and React Native) with fast, cache-friendly access to component source code, demos, and directory structures, empowering AI-driven development workflows. The project emphasizes production-readiness with Docker Compose, SSE transport for multi-client deployments, and smart caching to optimize GitHub API usage while providing rich metadata and usage patterns for rapid prototyping and learning across frameworks.

    Figma MCP server

    Figma MCP server

    The Figma MCP server enables design context delivery from Figma files to AI agents and code editors, empowering teams to generate code directly from design selections. It supports both a remote hosted server and a locally hosted desktop server, allowing seamless integration with popular editors through Code Connect and a suite of tools that extract design context, metadata, variables, and more. This guide covers enabling the MCP server, configuring clients (VS Code, Cursor, Claude Code, and others), and using a curated set of MCP tools to fetch structured design data for faster, more accurate code generation. It also explains best practices, prompts, and integration workflows that help teams align generated output with their design systems. The documentation includes concrete JSON examples for configuring servers in editors like VS Code and Cursor, as well as command examples for Claude Code integration and plugin installation.

    MarkItDown MCP

    MarkItDown MCP

    MarkItDown-MCP is a lightweight MCP (Model Context Protocol) server provided as the markitdown-mcp package. It exposes a STDIO, Streamable HTTP, and SSE MCP server designed for calling MarkItDown to convert content to Markdown. The package focuses on simplicity and accessibility, enabling you to run the MCP server locally via a simple CLI, or in Docker for containerized workflows, with integration options for Claude Desktop. The core capability is exposed through a single tool, convert_to_markdown(uri), which accepts a URI in http:, https:, file:, or data: schemes to fetch content and convert it to Markdown. This MCP server is easy to install with pip and can be used in various transport modes, including STDIO and HTTP/SSE, making it a flexible choice for automations and integrations.

    Chrome MCP Server

    Chrome MCP Server

    Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search. It leverages your existing Chrome environment, including login states and configurations, to allow large language models and chatbots to control the browser natively without needing to launch a separate automation process. The project emphasizes privacy by remaining fully local and offers capabilities such as cross-tab context, streamable HTTP communication, and a built-in vector database for semantic search and content analysis. As an early-stage project, it includes a growing set of tools for browser control, inspection, and automation, with ongoing development to broaden compatibility and features.

    MCP server for Appwrite docs

    MCP server for Appwrite docs

    The MCP server for Appwrite docs enables LLMs and code-generation tools to interact with comprehensive Appwrite documentation. It empowers AI assistants to access up-to-date API references, SDK guides, and implementation examples, facilitating intelligent code generation, troubleshooting, and best-practice guidance directly from the official docs. This MCP brings real-time context, semantic search, and seamless integration with popular editors and IDEs to accelerate development workflows around Appwrite's APIs and SDKs.

    Appwrite MCP server

    Appwrite MCP server

    Appwrite MCP server is a Model Context Protocol server that enables AI models to interact with Appwrite’s backend. It provides a curated set of MCP tools to manage databases, users, functions, teams, and more within your Appwrite project, enabling powerful AI-assisted workflows and natural-language interactions with your backend. The server ships with the Databases tools enabled by default to keep prompts within context limits and can be extended by enabling additional APIs via command-line flags. This makes it easier to build AI-powered applications that leverage Appwrite APIs securely and efficiently.