Connect Hugging Bay

Add Hugging Bay's bounded open-model metadata tools to Claude, Cursor, Cline, OpenClaw, ChatGPT, or another MCP/OpenAPI-capable assistant.

MCP (Claude Desktop / Claude Code / Cursor / Cline / OpenClaw)

{
  "mcpServers": {
    "hugging-bay": {
      "url": "https://huggingbay.xyz/api/mcp"
    },
    "bay-run": {
      "url": "https://run.huggingbay.xyz/mcp/"
    }
  }
}

hugging-bay supplies bounded public catalog metadata and evidence. bay-run supplies the separate specialist coprocessor; it does not proxy through Hugging Bay. Bay Run tool calls require its resource-bound OAuth bearer: compatible MCP clients follow the endpoint's protected-resource metadata automatically; otherwise mint the free MCP token through the Bay Run quickstart. Keep that token out of shared configuration files. The default Hugging Bay discovery profile exposes 10 bounded metadata tools (including the ready-to-run deployment_plan). The separate public verify profile exposes 17 read-only verification tools; publisher/full remain authenticated, and full-profile access is never inferred from the presence of an Authorization header. Test: curl -s https://huggingbay.xyz/api/mcp -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

OpenAPI (ChatGPT Actions / custom GPTs / any HTTP agent)

Import the REST contract from https://huggingbay.xyz/openapi.json. Start with /api/agents/find-model, /api/agents/recommend-prose, /api/v1/artifacts/{id}/report.

Hosted-file metadata

Inspect explicit hosted-file rows through the bounded file inventory API. Hugging Bay does not claim a drop-in Hugging Face endpoint or runtime-compatible bundle during containment.

Machine-readable guides