get_source_request_status — hugging bay MCP Tool Read-only
get_source_request_status
(get source request status) is one of 16 tools on the
hugging bay
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_source_request_status from your client
- Claude Code hugging bay get_source_request_status run in your project directory
- Claude Desktop hugging bay get_source_request_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hugging bay get_source_request_status ~/.cursor/mcp.json
- VS Code hugging bay get_source_request_status .vscode/mcp.json
- Zed hugging bay get_source_request_status ~/.config/zed/settings.json
- Windsurf hugging bay get_source_request_status ~/.codeium/windsurf/mcp_config.json
- Cline hugging bay get_source_request_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hugging bay get_source_request_status ~/.gemini/settings.json
- Grok hugging bay get_source_request_status .mcp.json (in your project root)
- ChatGPT hugging bay get_source_request_status Settings → Connectors → Advanced → Developer mode
- Claude.ai hugging bay get_source_request_status Settings → Connectors → Add custom connector
- LangChain hugging bay get_source_request_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hugging-bay https://huggingbay.xyz/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.