work_anywhere_scope — RemoShift Remote Jobs MCP Tool
work_anywhere_scope
(work anywhere scope) is one of 5 tools on the
RemoShift Remote Jobs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call work_anywhere_scope from your client
- Claude Code RemoShift Remote Jobs work_anywhere_scope run in your project directory
- Claude Desktop RemoShift Remote Jobs work_anywhere_scope ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RemoShift Remote Jobs work_anywhere_scope ~/.cursor/mcp.json
- VS Code RemoShift Remote Jobs work_anywhere_scope .vscode/mcp.json
- Zed RemoShift Remote Jobs work_anywhere_scope ~/.config/zed/settings.json
- Windsurf RemoShift Remote Jobs work_anywhere_scope ~/.codeium/windsurf/mcp_config.json
- Cline RemoShift Remote Jobs work_anywhere_scope ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RemoShift Remote Jobs work_anywhere_scope ~/.gemini/settings.json
- Grok RemoShift Remote Jobs work_anywhere_scope .mcp.json (in your project root)
- ChatGPT RemoShift Remote Jobs work_anywhere_scope Settings → Connectors → Advanced → Developer mode
- Claude.ai RemoShift Remote Jobs work_anywhere_scope Settings → Connectors → Add custom connector
- LangChain RemoShift Remote Jobs work_anywhere_scope pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jobs https://remoshift.com/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.