Connect your AI agent to Shopletzy
Authorize a compatible MCP client, choose store access, and run your first store task.
Connect ChatGPT, Codex, Claude, or another compatible AI agent to Shopletzy to read store information and carry out supported store-management tasks. Start with a focused task and expand access as you need it.
Explore AI store management for examples and a capability overview.
Before you start
Shopletzy works with any AI client that supports remote MCP over Streamable HTTP with OAuth authorization, including ChatGPT, Codex, and Claude. Check the requirements below and verify a store read after connecting.
You need:
- A Shopletzy account with an eligible store and the merchant permissions needed for your task.
- An AI client that supports remote MCP over Streamable HTTP with OAuth authorization, including discovery and the S256 PKCE authorization-code flow. Local stdio configuration and manually pasted bearer tokens are not the hosted connection flow.
- Permission to add remote MCP servers in that client. Availability, account requirements, and setup labels vary by provider.
Existing Shopletzy plan requirements and resource limits still apply. Your AI provider may charge for its own service. This guide does not imply that every AI client or subscription supports this connection.
1. Add the Shopletzy server
Open your client’s remote MCP or custom connector settings. Add a server named Shopletzy using this URL:
https://app.shopletzy.com/mcpChoose OAuth authorization if your client asks. It should discover Shopletzy’s authorization server and start the connection process. There is no Shopletzy API key or client secret to paste into a chat.
This is a protocol endpoint, not a web page to open for sign-in. Do not use the testing server or a local stdio command for a production store.
2. Sign in and choose access
Your client opens Shopletzy’s authorization page. Check that the page is on app.shopletzy.com, then sign in with Google or an email code.
Review the requesting application’s details, select the stores it should access, and review every offered permission. Turn off writes you do not need. Store selection may also offer access to eligible stores you create later; enable that only if you intend to authorize them too.
Complete consent and return to your client. Keep credentials within the client’s connection settings; do not share access tokens, refresh tokens, email codes, or signed preview confirmations in messages or screenshots.
3. Verify a read first
Ask your agent:
List the Shopletzy stores this connection can access. Do not make changes.
Check that the result includes the intended store. Then try a focused read:
Show the five newest products in this store, including their current descriptions. Do not change anything.
If your client has no tool access, finish its connection process and refresh the tool list. If a store is missing, check your consent, current merchant role, and store eligibility.
4. Give your agent a bounded task
For a first write, choose a product description you can easily restore. Keep a copy of the existing text and provide the exact store and product:
For this product, improve the description using only its existing facts. Do not change the name, price, images, or stock. Preview the change, check it against these instructions, apply it, and read back the saved description.
Review the result in Shopletzy. Restore the original text if this was only a connection test.
Supported writes follow preview → apply. The agent can review and apply an authorized preview itself; a person does not need to approve every individual tool call. Previews expire after ten minutes, and changes to the underlying data require a fresh preview. Successful operations support idempotent retries for 24 hours when the same operation ID is reused. An agent should not generate a fresh operation ID to retry an ambiguous result.
Set standing instructions
You can authorize recurring types of work with clear limits. For example:
You may improve product descriptions using only existing product facts. Preserve names, prices, stock, and images. Apply the updates and report what changed. Ask before publishing announcements or changing orders.
Your AI client provides the agent runtime and any scheduling. Connecting Shopletzy does not schedule tasks or start an agent running in the background.
Supported work and current limits
| Area | Supported work | Boundaries to know |
|---|---|---|
| Products and categories | Product creation; supported text/SEO, image, variant and pricing updates; category management and product assignment | Some broader product fields and bulk operations remain in admin. Category images and reparenting are not supported. |
| Inventory | Outlet inventory reads and available-stock updates | Reserved and committed allocations are protected. |
| Orders | Reads, acceptance, supported shipping/pickup/completion transitions, return status, and eligible COD cancellation/decline | Online-payment cancellations/refunds, order editing, and invoicing remain in admin. Recording a return does not refund or restock. |
| Promotions and charges | Supported promotion and additional-charge management | Free-product promotions are not supported. Existing commerce validation still applies. |
| Announcements | Read, draft, edit, publish, archive, and delete | Publishing can notify customers. Announcement CTA editing is not supported. |
| Store content and setup | Supported store/outlet details, hours, delivery areas, FAQs, collections, and images | Existing resource limits and permission checks apply. |
| Customers and insights | Store-scoped customer reads, order history, and sales insights | Customer tools are read-only. Agent access shares selected store data with your chosen client. |
Available actions depend on your granted scopes, live merchant permissions, store eligibility, and supported operation rules. Never test the connection by accepting real orders, completing fulfillment, or publishing customer-facing content unless that work is explicitly authorized.
Review, change, or revoke access
Open Shopletzy connected apps to review connections and revoke access. Revocation blocks subsequent requests; it does not undo completed work, erase data already received by the client, or guarantee that in-flight work stops.
Existing connections do not gain new scopes automatically. When you need more capabilities, reconnect through your client and approve the additional access. To reduce access, review the connection’s controls or revoke it and reconnect with narrower permissions.
Clients can refresh access while a connection remains valid. A sign-in prompt after expiry or revocation is expected. Testing and production tokens are not interchangeable.
Troubleshooting
- The URL opens an error in my browser. Add it in the MCP client’s settings; it is not a sign-in landing page.
- OAuth or remote MCP is unavailable. Check your client’s current documentation and account entitlements. A local-only or manually configured token client does not provide this hosted OAuth journey.
- The wrong stores appear. Verify the Google/email identity, consent selection, current role, and store eligibility.
- A write is denied. Check the specific permission and operation limits. Adding new capabilities requires renewed consent.
- A preview expired or became stale. Read current data and create a fresh preview before applying.
- A request timed out. Preserve its operation ID and follow the tool’s retry behavior. Check the saved state before starting new work.
For help, contact Shopletzy with your client name and a description of the failure. Do not include credentials, signed confirmations, or customer contact details.