Skip to main content
Back to the Hugging Face MCP server

MCP Gateway · Claude

Hugging Face icon

Connect Hugging Face to Claude

Analysts, researchers and product managers often need to know what is new in machine learning without reading every release. Added to Claude as a custom connector through the Speakeasy MCP Gateway, Hugging Face lets people search papers and models in a conversation, and run Space tasks like OCR on their own files.

Category
AI & search
Tools
10
Authentication
OAuth
Claude
Web, desktop and mobile

Behind the MCP Gateway

Run Hugging Face MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Hugging Face call inspected and logged.

Deploy on MCP Gateway

Set up

Add Hugging Face to Claude in 4 steps

  1. 01

    Add Hugging Face from the catalog

    An admin finds Hugging Face in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Hugging Face uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Hugging Face

    Give teams the mcp:connect scope on the Hugging Face server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Hugging Face to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Hugging Face from Claude

    The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Hugging Face needs its own OAuth grant, so each person connects it once. Until they do, Hugging Face calls fail while the rest of the gateway keeps working.

    From then on, Hugging Face's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Hugging Face

Summarize recent research on a topic

Ask Claude for recent papers on a topic like speech recognition, with links, and get a plain summary of what each one claims.

paper_search

Extract text from a scanned page

Claude runs an OCR task through a Hugging Face Space on a scanned document, then tidies the text into something you can quote.

dynamic_space

Explain a model before a decision

When a vendor names the model behind their product, ask Claude for its Hub details and an explanation of what the model is meant for.

hub_repo_searchhub_repo_details

Tools

10 tools

Each Hugging Face tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.

hf_whoami

Hugging Face tools are being used by the authenticated user

hub_repo_details

Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified.

See all 10 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.

Tool logs

Gateway

Every Hugging Face call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Hugging Face tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Hugging Face can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Hugging Face prompts in Claude be checked before inference?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do people on Pro and Max plans add Hugging Face to Claude?
Each person adds the gateway URL themselves under Customize > Connectors > Add custom connector.
How do Claude users get Hugging Face?
An admin adds Hugging Face from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Hugging Face tools their access allows.
Are Hugging Face calls from Claude logged?
Yes. Hugging Face calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Hugging Face in other clients

AI everywhere.

Control here.