Integrations · Development

Connect Hugging Face to Well

Connect Hugging Face to make it reachable from conversation and your agents in Well. Hugging Face exposes no structured records to sync today, so this is a reach connection, not a data feed.

Connect Hugging FaceSee what Well does

What Well pulls from Hugging Face

Hugging Face feeds Hugging Face into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Hugging Face’s access.

From Hugging Face		In Well	Relation
Hugging Face		Workspace context	Reachable from

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Hugging Face → Well

What Well does with your Hugging Face connection

Connect

Connect Hugging Face over OAuth (MCP DCR): Well registers a client through Hugging Face's OAuth Dynamic Client Registration and you approve on Hugging Face's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Connecting Hugging Face makes it reachable from your workspace; Hugging Face exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Hugging Face adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Hugging Face is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Hugging Face unlocks

Ask in plain language. Well answers from your connected Hugging Face connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Hugging Face connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Hugging Face connection…

Connect Hugging Face in three steps

01
Authorise Hugging Face via MCP
From Well's Connections panel, search for Hugging Face and click Connect. Well discovers Hugging Face's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Hugging Face's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverhuggingface.co/mcp
02
Make it reachable
The connection puts Hugging Face within reach of your workspace and its agents. Hugging Face exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Hugging Face in the same place it reaches the rest of your stack. If Hugging Face later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Hugging Face stays secure with Well

Well connects to Hugging Face's MCP server (huggingface.co/mcp) via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Hugging Face secret. Because Hugging Face maps no structured entity today, the token simply makes Hugging Face reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Hugging Face.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestshuggingface.co/mcp

Read Hugging Face records
Resources the Hugging Face MCP server exposes, scoped by your OAuth approval.
granted
Reach Hugging Face from your workspace
The grant makes Hugging Face reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Hugging Face.
granted
Modify or delete Hugging Face records
Not granted; Hugging Face is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Hugging Face passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Hugging Face’s admin panel.

Frequently asked questions about Hugging Face and Well

How do I connect Hugging Face to Well, and how long does it take?

Choose Hugging Face in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Hugging Face within reach of your workspace and its agents.

What does Well sync from Hugging Face today?

No structured record, and the page is candid about that. Hugging Face exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.

If nothing is synced, what does connecting Hugging Face give me?

It lets an agent working in your workspace reach Hugging Face in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Hugging Face does not expose.

Will Hugging Face ever bring records into the workspace?

Only if and when Hugging Face exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.

What happens if I disconnect Hugging Face?

Disconnecting Hugging Face in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Hugging Face from the set of tools your agents can reach through Well.