Job-to-be-Done Answer — Curie Commerce MCP Resource
Job-to-be-Done Answer
is one of 14 resources on the
Curie Commerce
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Job-to-be-Done Answer from your client
- Claude Code Curie Commerce Resource/Job-to-be-Done Answer run in your project directory
- Claude Desktop Curie Commerce Resource/Job-to-be-Done Answer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Curie Commerce Resource/Job-to-be-Done Answer ~/.cursor/mcp.json
- VS Code Curie Commerce Resource/Job-to-be-Done Answer .vscode/mcp.json
- Zed Curie Commerce Resource/Job-to-be-Done Answer ~/.config/zed/settings.json
- Windsurf Curie Commerce Resource/Job-to-be-Done Answer ~/.codeium/windsurf/mcp_config.json
- Cline Curie Commerce Resource/Job-to-be-Done Answer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Curie Commerce Resource/Job-to-be-Done Answer ~/.gemini/settings.json
- Grok Curie Commerce Resource/Job-to-be-Done Answer .mcp.json (in your project root)
- ChatGPT Curie Commerce Resource/Job-to-be-Done Answer Settings → Connectors → Advanced → Developer mode
- Claude.ai Curie Commerce Resource/Job-to-be-Done Answer Settings → Connectors → Add custom connector
- LangChain Curie Commerce Resource/Job-to-be-Done Answer pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.