Hugging Bay MCP

Use the pinned npm stdio package or the live streamable-HTTP endpoint. The npm publication observation is version 0.1.5; official MCP Registry submission and approval are not claimed.

npx -y hugging-bay-mcp@0.1.5

stdio client configuration

{
  "mcpServers": {
    "hugging-bay": {
      "command": "npx",
      "args": ["-y", "hugging-bay-mcp@0.1.5"]
    }
  }
}

Cursor: catalog plus execution

Install both services when the agent must discover evidence in Hugging Bay and execute bounded specialist work through Bay Run.

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

Hugging Bay metadata tools are public. Bay Run tool calls require its resource-bound OAuth bearer; compatible MCP clients follow the endpoint's protected-resource metadata automatically. Otherwise use the Bay Run quickstart to mint the free MCP token. Keep the token out of shared configuration files.

Supported protocol

This release accepts MCP protocol version 2025-06-18. Unsupported values are rejected during initialization.

Verify the npm package

npm view hugging-bay-mcp@0.1.5 version dist.integrity dist.tarball

Confirm that the returned integrity value and tarball URL match the live channel above. The npm registry package page is the package publication authority; a source manifest is not proof of registry submission.

Remote endpoint

Clients that support streamable HTTP can connect directly to https://huggingbay.xyz/api/mcp. Discovery is available at https://huggingbay.xyz/.well-known/mcp.json.