get_request_status — One Coworking MCP Tool Read-only
get_request_status
(get request status) is one of 10 tools on the
One Coworking
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_request_status from your client
- Claude Code One Coworking get_request_status run in your project directory
- Claude Desktop One Coworking get_request_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor One Coworking get_request_status ~/.cursor/mcp.json
- VS Code One Coworking get_request_status .vscode/mcp.json
- Zed One Coworking get_request_status ~/.config/zed/settings.json
- Windsurf One Coworking get_request_status ~/.codeium/windsurf/mcp_config.json
- Cline One Coworking get_request_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI One Coworking get_request_status ~/.gemini/settings.json
- Grok One Coworking get_request_status .mcp.json (in your project root)
- ChatGPT One Coworking get_request_status Settings → Connectors → Advanced → Developer mode
- Claude.ai One Coworking get_request_status Settings → Connectors → Add custom connector
- LangChain One Coworking get_request_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.onecoworking.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 15 October 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.