[FEEDBACK] Hugging Face MCP
Hugging Face MCP
This discussion is dedicated to providing feedback on the HF MCP.
About HF MCP
The Hugging Face Model Control Protocol (MCP) is a new server that enables seamless integration between the Hugging Face Hub and any AI assistant that supports MCP, such as VSCode, Cursor, or Claude Desktop. It provides a standardized way for assistants to access and interact with Hugging Face tools and resources, including Spaces, semantic search in Papers, and model or dataset exploration. Additionally, MCP allows assistants to connect to any compatible Gradio app, extending their capabilities with machine learning-powered applications developed by the community.
This feature is experimental ⚗️ and will continue to evolve
Let us know what you think 💬👇
Financial data international cyber guaranteed security
.
This MCP server can't be used by ChatGPT to search information because it doesn't implement our specification: search action not found
https://platform.openai.com/docs/mcp#create-an-mcp-server
Please add to your MCP Server "search" and "fetch" tools according to OpenAI MCP specification.
This MCP server can't be used by ChatGPT to search information because it doesn't implement our specification: search action not found
https://platform.openai.com/docs/mcp#create-an-mcp-serverPlease add to your MCP Server "search" and "fetch" tools according to OpenAI MCP specification.
Hi @markba , this update is in our plans and should come soon 👍 cc @evalstate
not good
how can i get gemini-cli to connect to this mcp server?
Hi @bivalve -- have you followed the instructions for connecting Gemini here: https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md ? Can you say more about the error you are seeing?
- https://huggingface.co/learn/mcp-course/unit1/hf-mcp-server#get-started bullet 2 promises Zed but there is no Zed option provided
Fails in VScode , Kiro
I have claude connected to Hugging face connector and when trying to use HF to generate an image coming back with this:
"The problem is clear: The Hugging Face MCP connector in your Claude setup has gradio=none configured, which completely blocks all image generation invocations regardless of which space I try to use."
I don't see a way to change this, can anyone help?
I'm having the same problem as @jj210tx after following this guide https://huggingface.co/blog/claude-and-mcp
I have claude connected to Hugging face connector and when trying to use HF to generate an image coming back with this:
"The problem is clear: The Hugging Face MCP connector in your Claude setup has gradio=none configured, which completely blocks all image generation invocations regardless of which space I try to use."
I don't see a way to change this, can anyone help?
Hi @jj210tx @gqbit -- Anthropic updated their content policy so the connector by default has images disabled. If you "add a custom connector" instead, you can use the URL https://huggingface.co/mcp?login and all should work normally.
I have claude connected to Hugging face connector and when trying to use HF to generate an image coming back with this:
"The problem is clear: The Hugging Face MCP connector in your Claude setup has gradio=none configured, which completely blocks all image generation invocations regardless of which space I try to use."
I don't see a way to change this, can anyone help?Hi @jj210tx @gqbit -- Anthropic updated their content policy so the connector by default has images disabled. If you "add a custom connector" instead, you can use the URL
https://huggingface.co/mcp?loginand all should work normally.
This works but it should be noted that Custom Connectors require a paid Claude plan.
Remove gradio_none
Can’t configure through Claude code
nothing happened when claude mcp add hf-mcp-server -t http "https://huggingface.co/mcp?login"
can you just remove claude code to prevert someone poor tried many times?
Love it
Why is IBM Bob not listed as an MCP Client option?
One bit of feedback from operating MCP/tool-using agents: the next layer that feels important is a consistent run record around tool calls.
For example, when an assistant calls an HF MCP tool, it would be useful for the host/client to preserve:
- run/session id
- user turn id
- tool call id
- host/client name + version
- selected MCP server/tool
- input/output metadata
- approval state if any
- final artifact or action
The big thing I would avoid is treating the model's explanation as authorization evidence. It is useful context for review, but policy should come from deterministic metadata: user/session, tool metadata, scopes, environment, and approval state.
This is the same direction we are exploring with Armorer for local/self-hosted agents: make runs, tools, approvals, and artifacts inspectable instead of leaving agent execution as an opaque chat transcript.
https://github.com/ArmorerLabs/Armorer
Curious if HF MCP already has a preferred place for this kind of audit/run metadata, or if it is expected to live entirely in the host application for now.