Skip to main content
Back to the Hugging Face MCP server

MCP Gateway · OpenCode

Hugging Face icon

Connect Hugging Face to OpenCode

Some questions about the Hub are structured queries: which organization's models gained the most likes this month, or how many datasets a team has published. OpenCode users can ask them from the terminal after adding the server as a remote entry in the mcp config. The OpenCode plugin sends each prompt and tool call to Speakeasy to allow or deny.

Category
AI & search
Tools
10
Authentication
OAuth
OpenCode
Terminal

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 OpenCode 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. OpenCode 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 OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Hugging Face from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Hugging Face

Query the Hub like a database

Ask OpenCode to rank an organization's models by likes, count its datasets or list its recent activity, and get compact structured results back.

hf_hub_query

Track a model's discussions

Before upgrading a model you depend on, check its recent discussions and repository details for reported problems with the new version.

hf_hub_queryhub_repo_details

Aggregate a search across repo types

Search models, datasets and Spaces for a keyword in a single call, and get a link to each repository OpenCode found, without switching to the browser.

hub_repo_search

Tools

10 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

How does Hugging Face get into OpenCode?
OpenCode doesn't receive MCP servers from plugins. Copy the server URL from its hosted install page, add it to the mcp block with type set to remote, then restart OpenCode and sign in.
Does the device agent help with OpenCode?
Yes. The device agent installs and maintains the observability package that sends OpenCode's prompts, tool calls and usage to Speakeasy.
How do OpenCode users get Hugging Face?
An admin adds Hugging Face from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Hugging Face tools their access allows.
Are Hugging Face calls from OpenCode 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.