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 2026-07-28, 2025-11-25, 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. Browser-readable profile and tool discovery is at https://huggingbay.xyz/api/mcp/info; the generated MCP manifest is at https://huggingbay.xyz/.well-known/mcp.json.

Observed tools/list contract

The remote endpoint is self-describing over JSON-RPC 2.0. Call tools/list to discover the selected profile's tools (discovery by default), then tools/call to run one. Public reads need no token. This is the observed contract on the Hugging Bay side — not only the fixed Bay Run demo Pins.

curl -fsS 'https://huggingbay.xyz/api/mcp' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Representative public tools returned by tools/list:

• Discovery: search_artifacts, resolve_artifact, get_artifact, find_runnable
• Catalog files: list_files, get_artifact_card
• Download and deployment: deployment_plan, get_serve_decision
• Source and citation metadata: get_source_coverage, get_citation_pack

The default hosted discovery list is published under x-mcp.publicTools; x-mcp.profiles lists the tools, counts and authorization for discovery, verify, publisher, intent and full in the OpenAPI document. Live hosted discovery reports the selected profile; the MCP discovery manifest reports the default discovery list and profile counts. The verify profile is public and opt-in; full requires admin authorization. x-mcp.authenticatedTools is registered inventory, not the default list. Tool arguments and response shapes are the same JSON the REST endpoints return.