apply_to_job — resume builder ats checker MCP Prompt
apply_to_job
is one of 2 prompts on the
resume builder ats checker
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke apply_to_job from your client
- Claude Code resume builder ats checker Prompt/apply_to_job run in your project directory
- Claude Desktop resume builder ats checker Prompt/apply_to_job ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor resume builder ats checker Prompt/apply_to_job ~/.cursor/mcp.json
- VS Code resume builder ats checker Prompt/apply_to_job .vscode/mcp.json
- Zed resume builder ats checker Prompt/apply_to_job ~/.config/zed/settings.json
- Windsurf resume builder ats checker Prompt/apply_to_job ~/.codeium/windsurf/mcp_config.json
- Cline resume builder ats checker Prompt/apply_to_job ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI resume builder ats checker Prompt/apply_to_job ~/.gemini/settings.json
- Grok resume builder ats checker Prompt/apply_to_job .mcp.json (in your project root)
- ChatGPT resume builder ats checker Prompt/apply_to_job Settings → Connectors → Advanced → Developer mode
- Claude.ai resume builder ats checker Prompt/apply_to_job Settings → Connectors → Add custom connector
- LangChain resume builder ats checker Prompt/apply_to_job pip install langchain-mcp-adapters
Other prompts on this server
resume builder ats checker also offers 2 resources — 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 26 September 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.