Hugging Face repository files, commits, branches and discussions (BYOK)

Hugging Face repository files, commits, branches and discussions (BYOK) — connector documentation

• MCP endpoint: https://byok-huggingface-repo-history.connectorbay.com/mcp
• REST API: POST https://byok-huggingface-repo-history.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-huggingface-repo-history.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Hugging Face Repo History Hugging Face access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-huggingface-repo-history.connectorbay.com/health · Tool schemas: https://byok-huggingface-repo-history.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-huggingface-repo-history · agent@connectorbay.com

What Hugging Face repository files, commits, branches and discussions (BYOK) is for

Hugging Face repository files, commits, branches and discussions (BYOK) lets an AI assistant read your own Hugging Face Repo History data through the Hugging Face Repo History API with a key you supply (Hugging Face access token). Read-only: 6 tools (list_repo_tree, list_repo_commits, list_repo_refs, list_repo_discussions, get_repo_discussion, list_repo_lfs_files). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to huggingface.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hugging Face Repo History. Hugging Face Repo History and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What files are in the Hugging Face model openai-community/gpt2 and how big are they?"
• "What are the latest commits of Hugging Face model openai-community/gpt2?"
• "Which branches and tags does Hugging Face model openai-community/gpt2 have?"
• "What open pull requests does Hugging Face model openai-community/gpt2 have?"
• "Is pull request 7 on Hugging Face model openai-community/gpt2 mergeable?"
• "How much LFS storage does my Hugging Face repo alice/my-model use?"

What it does

• list_repo_tree: List the files and folders of a repository at a revision with type, path, size in bytes, git object id and LFS size. Returns the first page of entries. Reads repository metadata only; file contents are not downloaded.
• list_repo_commits: List the commits of a repository at a revision, newest first, with commit id, title, message, date and authors. Reads repository metadata only; file contents are not downloaded.
• list_repo_refs: List the branches, tags and conversion refs of a repository with their names, ref paths and target commit ids. Reads repository metadata only; file contents are not downloaded.
• list_repo_discussions: List discussions and pull requests of a repository with number, title, status, pull request flag, author and creation time; 'count' is the total. Page index starts at 0. Reads repository metadata only; file contents are not downloaded.
• get_repo_discussion: Get one discussion or pull request by number: title, status, pull request flag, author, target branch, merge commit and conflicting files. Comment text is not returned. Reads repository metadata only; file contents are not downloaded.
• list_repo_lfs_files: List the large (LFS) files stored for a repository with object id, filename, size, push time and ref; useful for storage usage. Reads repository metadata only; file contents are not downloaded.

BYOK key

You bring your own Hugging Face Repo History Hugging Face access token (https://huggingface.co/settings/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to huggingface.co over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/hf_api.py (the API this connector calls, with a BYOK key)

Live from the Hugging Face Repo History API (huggingface.co) with a BYOK key; documentation: https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/hf_api.py. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hugging Face Repo History. Hugging Face Repo History and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Hugging Face Repo History account.

Built for: Worldwide. Languages: English.

Hugging Face repository files, commits, branches and discussions (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Hugging Face repository files, commits, branches and discussions (BYOK) is. Hugging Face repository files, commits, branches and discussions (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Hugging Face Repo History data: Read the file tree, commit history, branches and tags, discussions and pull requests, and LFS files of Hugging Face model, dataset and Space repositories with your own access token. You bring your own Hugging Face Repo History Hugging Face access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Hugging Face Repo History call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to huggingface.co, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Hugging Face Repo History rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Hugging Face Repo History receives. The request we make on your behalf, including the key and the arguments, under Hugging Face Repo History's own terms and privacy policy. Hugging Face Repo History acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Hugging Face Repo History gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Hugging Face Repo History data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Hugging Face Repo History (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Hugging Face Repo History at any time to end all access.

Children. Hugging Face repository files, commits, branches and discussions (BYOK) is a general-audience service operated by the adult using the assistant, under Hugging Face Repo History's own age rules.

Changes. We will post changes here with a new effective date.

Hugging Face repository files, commits, branches and discussions (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Hugging Face repository files, commits, branches and discussions (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Hugging Face repository files, commits, branches and discussions (BYOK) provides: Read the file tree, commit history, branches and tags, discussions and pull requests, and LFS files of Hugging Face model, dataset and Space repositories with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Hugging Face Repo History credentials and only access data you are allowed to access. Hugging Face Repo History's terms apply to your use of Hugging Face Repo History; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hugging Face Repo History. Hugging Face Repo History and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Hugging Face Repo History returns, lightly trimmed; it may be incomplete, delayed or changed by Hugging Face Repo History. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Hugging Face Repo History account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Hugging Face Repo History's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Hugging Face Repo History may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Hugging Face Repo History key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Hugging Face Repo History takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-huggingface-repo-history

Hugging Face repository files, commits, branches and discussions (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-huggingface-repo-history.connectorbay.com/mcp
• REST API: https://byok-huggingface-repo-history.connectorbay.com/openapi.json
• Live status: https://byok-huggingface-repo-history.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Hugging Face repository files, commits, branches and discussions (BYOK) never asks for them.