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