evaluate_for_vacancy — hr MCP Prompt

evaluate_for_vacancy is one of 4 prompts on the hr MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke evaluate_for_vacancy from your client

• Claude Code hr Prompt/evaluate_for_vacancy run in your project directory
• Claude Desktop hr Prompt/evaluate_for_vacancy ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor hr Prompt/evaluate_for_vacancy ~/.cursor/mcp.json
• VS Code hr Prompt/evaluate_for_vacancy .vscode/mcp.json
• Zed hr Prompt/evaluate_for_vacancy ~/.config/zed/settings.json
• Windsurf hr Prompt/evaluate_for_vacancy ~/.codeium/windsurf/mcp_config.json
• Cline hr Prompt/evaluate_for_vacancy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI hr Prompt/evaluate_for_vacancy ~/.gemini/settings.json
• Grok hr Prompt/evaluate_for_vacancy .mcp.json (in your project root)
• ChatGPT hr Prompt/evaluate_for_vacancy Settings → Connectors → Advanced → Developer mode
• Claude.ai hr Prompt/evaluate_for_vacancy Settings → Connectors → Add custom connector
• LangChain hr Prompt/evaluate_for_vacancy pip install langchain-mcp-adapters

Other prompts on this server

• how_to_connect
• send_vacancy_and_schedule
• prepare_for_interview

Read from the server itself, by connecting to it and calling prompts/list on 24 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.