who_is_alex — Alex Polonsky Profile MCP Prompt

who_is_alex is one of 2 prompts on the Alex Polonsky Profile MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke who_is_alex from your client

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

Other prompts on this server

• check_availability

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.