interior-spec — Colour Memory MCP Prompt

interior-spec is one of 8 prompts on the Colour Memory MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke interior-spec from your client

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

Other prompts on this server

• name-my-colour
• colour-strategy
• palette-for-concept
• image-generation-brief
• should-i-use-this-colour
• break-the-cliche
• name-my-product-range

Colour Memory 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.