MCP connector

Setup

1. Open your organization dashboard and go to Connector.
2. Create a connector token. Copy the URL — it is shown once.
3. Use the "Add it to Claude" link, or paste the URL into Claude under Settings → Connectors → Add custom connector.

The URL contains your token. Treat it like a password — anyone holding it can read and create cores in your organization through Claude and run product searches against them, and that usage is recorded against your organization. It cannot delete or edit anything: those stay on the REST API. Revoke it from the dashboard and it stops working immediately.

Tools

• create_coreCreate a core from 1-5 images, given as https URLs, base64 data URLs, or both. Returns immediately with a job id.
• get_coreFetch a core with its taste profile and generation status.
• get_jobCheck a taste generation job by its job id. get_core is usually better — it reports the same status and returns the taste in one call.
• get_tasteFetch just the taste profile text for a core.
• list_coresList the organization's cores, newest first.
• search_coresSearch cores by name, tags and style attributes. Synonym-aware.
• search_productsFind fashion products matching a core's taste. Returns the top 10 products.

The connector is data-only — it returns structured results, not interactive cards. It never exposes anything outside your own organization.

The connector shares the REST API's rate limits, and every cap counts both surfaces together — an agent cannot work around one by switching to the connector. create_core is limited to 5 core creations per minute per organization and search_products to 20 searches per minute per organization. Over either, the tool returns an error saying how many seconds to wait.

search_products only works on a core whose taste profile has finished generating. Ask for one that is still processing and the tool says so — wait a few seconds and try again rather than treating it as an empty result.