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