send_ready_ones — Job Spotter MCP Prompt
send_ready_ones
is one of 6 prompts on the
Job Spotter
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke send_ready_ones from your client
- Claude Code Job Spotter Prompt/send_ready_ones run in your project directory
- Claude Desktop Job Spotter Prompt/send_ready_ones ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Job Spotter Prompt/send_ready_ones ~/.cursor/mcp.json
- VS Code Job Spotter Prompt/send_ready_ones .vscode/mcp.json
- Zed Job Spotter Prompt/send_ready_ones ~/.config/zed/settings.json
- Windsurf Job Spotter Prompt/send_ready_ones ~/.codeium/windsurf/mcp_config.json
- Cline Job Spotter Prompt/send_ready_ones ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Job Spotter Prompt/send_ready_ones ~/.gemini/settings.json
- Grok Job Spotter Prompt/send_ready_ones .mcp.json (in your project root)
- ChatGPT Job Spotter Prompt/send_ready_ones Settings → Connectors → Advanced → Developer mode
- Claude.ai Job Spotter Prompt/send_ready_ones Settings → Connectors → Add custom connector
- LangChain Job Spotter Prompt/send_ready_ones pip install langchain-mcp-adapters
Other prompts on this server
Job Spotter also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.