Skip to main content
Back to the Hugging Face MCP server

MCP Gateway · ChatGPT

Hugging Face icon

Connect Hugging Face to ChatGPT

Content and marketing teams use Hugging Face Spaces for quick media tasks like text to speech or removing an image background. With the server available in ChatGPT through Speakeasy's plugin marketplace, people run those tasks from a chat. A workspace admin sets which roles get the plugin, and the gateway controls which of the 10 tools each can call.

Category
AI & search
Tools
10
Authentication
OAuth
ChatGPT
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 ChatGPT 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. ChatGPT connects to the Hugging Face server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect ChatGPT

    Import the organization's plugin marketplace into the ChatGPT workspace and set who gets each plugin.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Give the importing workspace admin collaborator access to the marketplace repository, and connect their GitHub account in ChatGPT under Plugins > GitHub > Manage.

    In ChatGPT, open Admin > Plugins > Add > Import marketplace.

    Set each plugin's installation policy, Installed or Available, per role.

    Enable the MCP servers the plugin connects to.

  4. 04

    Sign in and use Hugging Face from ChatGPT

    The first time ChatGPT 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 ChatGPT, limited to what the person's access allows, and every call lands in the gateway's tool logs.

The marketplace syncs from GitHub once a day. Use Sync now to pick up a change straight away.

Use cases

What ChatGPT users do with Hugging Face

Prepare product images

Ask ChatGPT to remove the background from a product photo using a Hugging Face Space task, then use the result in a slide or listing.

dynamic_space

Find an app for a one-off job

Describe what you need, such as turning a script into audio, and ChatGPT searches Spaces for ones that do it, with links to try them.

space_search

Answer a question about Hugging Face

When a colleague asks how Hugging Face handles something, ChatGPT searches the product documentation and answers with the page it used.

hf_doc_search

Tools

10 tools

Each Hugging Face tool can be allowed or denied per team and role at the MCP Gateway before ChatGPT 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 ChatGPT

The gateway covers every client the same way. The rest depends on what ChatGPT 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 ChatGPT. MCP-scoped policies are enabled per organization.

Conversation import

ChatGPT

ChatGPT activity can be imported through OpenAI's Compliance API for review after the fact. It can't block in real time.

  • The workspace import needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Can ChatGPT block a Hugging Face request as it happens?
No. ChatGPT activity can be imported through OpenAI's Compliance API for review after the fact, but it can't be blocked in real time. Tool access is still decided per role at the gateway.
Which ChatGPT plans can roll out Hugging Face through Speakeasy?
The workspace import needs a ChatGPT Business, Enterprise or Edu admin.
How do ChatGPT users get Hugging Face?
An admin adds Hugging Face from the Speakeasy MCP Catalog and grants access by team or role. Import the organization's plugin marketplace into the ChatGPT workspace and set who gets each plugin. Each person then sees only the Hugging Face tools their access allows.
Are Hugging Face calls from ChatGPT 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.