apply_to_job — career MCP Prompt

apply_to_job is one of 2 prompts on the career 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 career Prompt/apply_to_job run in your project directory
• Claude Desktop career Prompt/apply_to_job ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor career Prompt/apply_to_job ~/.cursor/mcp.json
• VS Code career Prompt/apply_to_job .vscode/mcp.json
• Zed career Prompt/apply_to_job ~/.config/zed/settings.json
• Windsurf career Prompt/apply_to_job ~/.codeium/windsurf/mcp_config.json
• Cline career Prompt/apply_to_job ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI career Prompt/apply_to_job ~/.gemini/settings.json
• Grok career Prompt/apply_to_job .mcp.json (in your project root)
• ChatGPT career Prompt/apply_to_job Settings → Connectors → Advanced → Developer mode
• Claude.ai career Prompt/apply_to_job Settings → Connectors → Add custom connector
• LangChain career Prompt/apply_to_job pip install langchain-mcp-adapters

Other prompts on this server

• upgrade_to_pro

career 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 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.