iShoppi

Create your online store

Create your iShoppi online store through your AI. Provide a store name and business category, review the proposed configuration, and confirm publication.

What you can ask

Create an online store called LittleNest for baby products.

MCP connector

Server URL: https://mcp.ishoppi.com/
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: IShoppi creates an initial online store for an authenticated account. Existing-store management, product editing, shopping comparisons and general business advice are outside these tools. The creation workflow starts with checkLogin to verify or establish the account connection. checkLogin and createStore use OAuth; missing or expired authentication is reported through the OAuth challenge. Preparation uses a store name and business category, which can be collected across conversation turns. Missing or ambiguous business information needs clarification. The store language follows the conversation unless the user requests a different language. The backend applies its supported-language fallback. prepareStore saves a temporary configuration and returns its preparationId, expiry and normalized store details. The proposed address is plain text because it is not active yet. Creating the store requires the user to explicitly confirm the returned configuration. A confirmation applies to that configuration while it remains valid; changed or expired configurations need a new review and confirmation. ChatGPT controls its own permission and authentication prompts. createStore accepts the preparationId of the confirmed configuration. A successful result supplies the full store and portal URLs and the service notices for the user. Preparation identifiers are internal references. The customer-facing creation confirmation presents all information supplied in customerResponse, translated into the conversation language, including the complete access notice and portal setup steps. Those setup steps explain the available product, logo, design, payment and delivery configuration. URLs remain unchanged and are displayed in full with https://. checkLogin reports authentication and the effects of that call, not whether the account already owns a store. An existing store prevents another creation through these tools. The supported path for additional stores is a request through https://ishoppi.com, not changing accounts or changing platform policy. Customer-facing explanations use the returned message and portal URL rather than internal error codes or numeric identifiers.

Tools

Changes data2

Deletes or can't be undone1

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.ishoppi.com/

OAuth

Protocol

MCP 2025-11-25

Instructions

IShoppi creates an initial online store for an authenticated account. Existing-store management, product editing, shopping comparisons and general business advice are outside these tools. The creation workflow starts with checkLogin to verify or establish the account connection. checkLogin and createStore use OAuth; missing or expired authentication is reported through the OAuth challenge. Preparation uses a store name and business category, which can be collected across conversation turns. Missing or ambiguous business information needs clarification. The store language follows the conversation unless the user requests a different language. The backend applies its supported-language fallback. prepareStore saves a temporary configuration and returns its preparationId, expiry and normalized store details. The proposed address is plain text because it is not active yet. Creating the store requires the user to explicitly confirm the returned configuration. A confirmation applies to that configuration while it remains valid; changed or expired configurations need a new review and confirmation. ChatGPT controls its own permission and authentication prompts. createStore accepts the preparationId of the confirmed configuration. A successful result supplies the full store and portal URLs and the service notices for the user. Preparation identifiers are internal references. The customer-facing creation confirmation presents all information supplied in customerResponse, translated into the conversation language, including the complete access notice and portal setup steps. Those setup steps explain the available product, logo, design, payment and delivery configuration. URLs remain unchanged and are displayed in full with https://. checkLogin reports authentication and the effects of that call, not whether the account already owns a store. An existing store prevents another creation through these tools. The supported path for additional stores is a request through https://ishoppi.com, not changing accounts or changing platform policy. Customer-facing explanations use the returned message and portal URL rather than internal error codes or numeric identifiers.