Connect your AI to Shopify

Give Claude, ChatGPT, Mistral or any MCP client secure access to Shopify — no official Shopify MCP server required. Proxoria turns Shopify's API into tools your AI can use, with per-user authentication and write actions gated by your approval.

What your AI can do with Shopify

Once connected, these tools appear automatically in your AI assistant:

  • list_abandoned_checkoutsread-only

    Returns a list of abandoned checkouts. A checkout is considered abandoned when a customer adds contact information but doesn't complete their purchase. Includes both abandoned and recovered checkouts. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_abandoned_checkoutsread-only

    Returns the count of abandoned checkouts for the given shop. Limited to a maximum of 10000 by default.

  • get_orderread-only

    The `order` query retrieves an order by its ID. This query provides access to comprehensive order information such as customer details, line items, financial data, and fulfillment status.

  • get_order_by_identifierread-only

    Return an order by an identifier.

  • get_order_payment_statusread-only

    Retrieves the status of a deferred payment by its payment reference ID. Use this query to monitor the processing status of payments that are initiated through payment mutations. Deferred payments are called payment terms in the API.

  • list_ordersread-only

    Returns a list of orders placed in the store, including data such as order status, customer, and line item details. Use the `orders` query to build reports, analyze sales performance, or automate fulfillment workflows. The `orders` query supports pagination, sorting, and filtering. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_ordersread-only

    Returns the number of orders in the shop. You can filter orders using search syntax or a `SavedSearch`, and set a maximum count limit to control query performance.

  • count_pending_ordersread-only

    The number of pendings orders. Limited to a maximum of 10000.

  • get_refundread-only

    Retrieves a refund by its ID. A refund represents a financial record of money returned to a customer from an order. It provides a comprehensive view of all refunded amounts, transactions, and restocking instructions associated with returning products or correcting order issues.

  • list_tender_transactionsread-only

    Transactions representing a movement of money between customers and the shop. Each transaction records the amount, payment method, processing details, and the associated `Order`. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • cancel_orderwrite · needs approval

    Cancels an order, with options for refunding, restocking inventory, and customer notification. Depending on refundMethod and restock, cancelling also refunds and restocks; notifyCustomer emails the customer. It cannot be undone.

  • capture_paymentwrite · needs approval

    Captures payment for an authorized transaction on an order. Use this mutation to claim the money that was previously reserved by an authorization transaction. Charges the customer's card for an amount that was only authorized. The charge is real.

  • close_orderwrite · needs approval

    Marks an open `Order` as closed. A closed order is one where merchants fulfill or cancel all `LineItem` objects and complete all financial transactions.

  • remove_order_customerwrite · needs approval

    Removes customer from an order.

  • set_order_customerwrite · needs approval

    Sets a customer on an order.

  • send_order_invoicewrite · needs approval

    Sends an email invoice for an `Order`. Emails the customer.

  • mark_order_as_paidwrite · needs approval

    Marks an order as paid by recording a payment transaction for the outstanding amount. Records a payment received outside Shopify (cash, bank transfer). No money moves.

  • open_orderwrite · needs approval

    Opens a closed order.

  • update_orderwrite · needs approval

    Updates the attributes of an order, such as the customer's email, the shipping address for the order, tags, and metafields associated with the order.

  • send_payment_reminderwrite · needs approval

    Sends an email payment reminder for a payment schedule. Emails the customer.

  • refund_orderwrite · needs approval

    Creates a refund for an order, allowing you to process returns and issue payments back to customers. Money goes back to the customer's payment method and cannot be taken back; pass notify to email them.

  • edit_orderwrite · needs approval

    Edit an existing order in one go: add variants or custom items, change quantities, add, update or remove discounts and shipping lines. The changes are staged in an edit session and committed together; if any change is refused, nothing is committed and the order is left as it was. Lines added in this call cannot be referenced by a later change of the same call. notifyCustomer emails the customer the updated order.

  • get_draft_orderread-only

    Retrieves a draft order by its ID. A draft order is an order created by a merchant on behalf of their customers. Draft orders contain all necessary order details (products, pricing, customer information) but require payment to be accepted before they can be converted into completed orders.

  • list_draft_order_delivery_optionsread-only

    Available delivery options for a `DraftOrder` based on the provided input. The query returns shipping rates, local delivery rates, and pickup locations that merchants can choose from when creating draft orders.

  • get_draft_order_tagread-only

    Returns a `DraftOrderTag` resource by ID.

  • list_draft_ordersread-only

    List of saved draft orders. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_draft_ordersread-only

    Returns the number of draft orders that match the query. Limited to a maximum of 10000 by default.

  • add_draft_order_tagswrite · needs approval

    Adds tags to multiple draft orders.

  • remove_draft_order_tagswrite · needs approval

    Removes tags from multiple draft orders.

  • calculate_draft_orderread-only

    Calculates the properties of a `DraftOrder` without creating it. Returns pricing information including `CalculatedDraftOrderLineItem` totals, shipping charges, applicable discounts, and tax calculations based on the provided `Customer` and `MailingAddress` information.

  • complete_draft_orderwrite · needs approval

    Completes a draft order and converts it into a regular order. The order appears in the merchant's orders list, and the customer can be notified about their order. Turns the draft into a real order.

  • create_draft_orderwrite · needs approval

    Creates a draft order with attributes such as customer information, line items, shipping and billing addresses, and payment terms. Draft orders are useful for merchants that need to:

  • create_draft_order_from_orderwrite · needs approval

    Creates a draft order from order.

  • delete_draft_orderwrite · needs approval

    Deletes a draft order.

  • duplicate_draft_orderwrite · needs approval

    Duplicates a draft order.

  • preview_draft_order_invoiceread-only

    Previews a draft order invoice email.

  • send_draft_order_invoicewrite · needs approval

    Sends an invoice email for a `DraftOrder`. The invoice includes a secure checkout link for reviewing and paying for the order. Use the `email` argument to customize the email, such as the subject and message. Emails the customer a checkout link.

  • update_draft_orderwrite · needs approval

    Updates a draft order.

  • get_fulfillmentread-only

    Retrieves a `Fulfillment` by its ID. A fulfillment is a record that the merchant has completed their work required for one or more line items in an `Order`. It includes tracking information, `LineItem` objects, and the status of the fulfillment.

  • get_fulfillment_orderread-only

    Returns a `FulfillmentOrder` resource by ID.

  • list_fulfillment_ordersread-only

    The paginated list of all fulfillment orders. The returned fulfillment orders are filtered according to the fulfillment order access scopes granted to the app. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_held_fulfillment_ordersread-only

    Returns a list of fulfillment orders that are on hold. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • cancel_fulfillmentwrite · needs approval

    Cancels an existing `Fulfillment` and reverses its effects on associated `FulfillmentOrder` objects. When you cancel a fulfillment, the system creates new fulfillment orders for the cancelled items so they can be fulfilled again.

  • create_fulfillmentwrite · needs approval

    Creates a fulfillment for one or more `FulfillmentOrder` objects. The fulfillment orders are associated with the same `Order` and are assigned to the same `Location`.

  • create_fulfillment_eventwrite · needs approval

    Creates a `FulfillmentEvent` to track the shipment status and location of items that have shipped. Events capture status updates like carrier pickup, in transit, out for delivery, or delivered.

  • cancel_fulfillment_orderwrite · needs approval

    Cancels a `FulfillmentOrder` and creates a replacement fulfillment order to represent the work left to be done. The original fulfillment order will be marked as closed.

  • hold_fulfillment_orderwrite · needs approval

    Applies a fulfillment hold on a fulfillment order.

  • mark_ready_for_pickupwrite · needs approval

    Marks fulfillment order line items as ready for customer pickup. When executed, this mutation automatically sends a "Ready For Pickup" notification to the customer.

  • merge_fulfillment_orderwrite · needs approval

    Merges a set or multiple sets of fulfillment orders together into one based on line item inputs and quantities.

  • move_fulfillment_orderwrite · needs approval

    Changes the location which is assigned to fulfill a number of unfulfilled fulfillment order line items.

  • release_fulfillment_order_holdwrite · needs approval

    Releases the fulfillment hold on a fulfillment order.

  • reschedule_fulfillment_orderwrite · needs approval

    Reschedules a scheduled fulfillment order.

  • split_fulfillment_orderwrite · needs approval

    Splits `FulfillmentOrder` objects by moving the specified `LineItem` objects and quantities into a new fulfillment order.

  • set_fulfillment_deadlinewrite · needs approval

    Sets the latest date and time by which the fulfillment orders need to be fulfilled.

  • update_fulfillment_trackingwrite · needs approval

    Updates tracking information for a fulfillment, including the carrier name, tracking numbers, and tracking URLs. You can provide either single or multiple tracking numbers for shipments with multiple packages.

  • get_returnread-only

    Retrieves a return by its ID. A return represents the intent of a buyer to ship one or more items from an order back to a merchant or a third-party fulfillment location.

  • calculate_returnread-only

    Calculates the financial outcome of a `Return` without creating it. Use this query to preview return costs before initiating the actual return process.

  • list_return_reasonsread-only

    Returns the full library of available return reason definitions. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_returnable_fulfillmentread-only

    Returns a `ReturnableFulfillment` resource by ID.

  • list_returnable_fulfillmentsread-only

    List of returnable fulfillments. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_reverse_deliveryread-only

    Lookup a reverse delivery by ID.

  • get_reverse_fulfillment_orderread-only

    Lookup a reverse fulfillment order by ID.

  • remove_from_returnwrite · needs approval

    Removes return and/or exchange lines from a return.

  • approve_return_requestwrite · needs approval

    Approves a customer's return request. If this mutation is successful, then the `Return.status` field of the approved return is set to `OPEN`.

  • cancel_returnwrite · needs approval

    Cancels a return and restores the items back to being fulfilled. Canceling a return is only available before any work has been done on the return (such as an inspection or refund).

  • close_returnwrite · needs approval

    Indicates a return is complete, either when a refund has been made and items restocked, or simply when it has been marked as returned in the system.

  • create_returnwrite · needs approval

    Creates a return from an existing order that has at least one fulfilled line item that hasn't yet been refunded. If you create a return on an archived order, then the order is automatically unarchived.

  • decline_return_requestwrite · needs approval

    Declines a return on an order. When a return is declined, each `ReturnLineItem.fulfillmentLineItem` can be associated to a new return. Use the `ReturnCreate` or `ReturnRequest` mutation to initiate a new return.

  • process_returnwrite · needs approval

    Processes a return by confirming which items customers return and exchange, handling their disposition, and optionally issuing refunds. This mutation confirms the quantities for `ReturnLineItem` and `ExchangeLineItem` objects previously created on the `Return`. Can issue the refund in the same step.

  • reopen_returnwrite · needs approval

    Reopens a closed return.

  • request_returnwrite · needs approval

    Creates a return request that requires merchant approval before processing. The return has its status set to `REQUESTED` and the merchant must approve or decline it.

  • create_reverse_deliverywrite · needs approval

    Creates a new reverse delivery with associated external shipping information.

  • update_reverse_delivery_shippingwrite · needs approval

    Updates a reverse delivery with associated external shipping information.

  • dispose_returned_itemswrite · needs approval

    Disposes reverse fulfillment order line items.

  • get_productread-only

    Retrieves a product by its ID. A product is an item that a merchant can sell in their store.

  • get_product_by_identifierread-only

    Return a product by an identifier.

  • get_product_duplicate_jobread-only

    Returns the product duplicate job.

  • get_product_operationread-only

    Returns a ProductOperation resource by ID.

  • list_product_tagsread-only

    Returns tags added to `Product` objects in the shop. Provides a paginated list of tag strings. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_product_typesread-only

    Returns a paginated list of product types assigned to products in the store. The maximum page size is 1000. The maximum page size is 1000. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_product_variantread-only

    Retrieves a product variant by its ID.

  • get_product_variant_by_identifierread-only

    Return a product variant by an identifier.

  • list_product_variantsread-only

    Retrieves a list of product variants associated with a product. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_product_variantsread-only

    Count of product variants. Limited to a maximum of 10000 by default.

  • list_product_vendorsread-only

    The list of vendors added to products. The maximum page size is 1000. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_productsread-only

    Retrieves a list of products in a store. Products are the items that merchants can sell in their store. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_productsread-only

    Count of products. Limited to a maximum of 10000 by default.

  • get_selling_plan_groupread-only

    Returns a `SellingPlanGroup` resource by ID.

  • list_selling_plan_groupsread-only

    Retrieves a paginated list of `SellingPlanGroup` objects that belong to the app making the API call. Selling plan groups are selling methods like subscriptions, preorders, or other purchase options that merchants offer to customers. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • search_product_taxonomyread-only

    Access to Shopify's standardized product taxonomy for categorizing products. The `Taxonomy` organizes products into a hierarchical tree structure with categories, attributes, and values.

  • create_product_bundlewrite · needs approval

    Creates a product bundle that groups multiple `Product` objects together as components. The bundle appears as a single product in the store, with its price determined by the parent product and inventory calculated from the component products.

  • update_product_bundlewrite · needs approval

    Updates a product bundle or componentized product.

  • create_productwrite · needs approval

    Creates a product with attributes such as title, description, vendor, and media.

  • delete_productwrite · needs approval

    Permanently deletes a product and all its associated data, including variants, media, publications, and inventory items. Permanent, with its variants and media.

  • duplicate_productwrite · needs approval

    Duplicates a product.

  • update_product_optionwrite · needs approval

    Updates an option on a product, such as size, color, or material. Each option includes a name, position, and a list of values. The combination of a product option and value creates a product variant.

  • create_product_optionswrite · needs approval

    Creates one or more options on a product, such as size, color, or material. Each option includes a name, position, and a list of values. The combination of a product option and value creates a product variant.

  • delete_product_optionswrite · needs approval

    Deletes one or more options from a product. Product options define the choices available for a product, such as size, color, or material.

  • reorder_product_optionswrite · needs approval

    Reorders the options and option values on a product, updating the order in which product variants are presented to customers.

  • reorder_product_mediawrite · needs approval

    Reorders media attached to a product, changing their sequence in product displays. The operation processes asynchronously to handle products with large media collections.

  • update_productwrite · needs approval

    Updates a product with attributes such as title, description, vendor, and media.

  • attach_variant_mediawrite · needs approval

    Appends existing media from a product to specific variants of that product, creating associations between media files and particular product options. This allows different variants to showcase relevant images or videos.

  • detach_variant_mediawrite · needs approval

    Detaches media from product variants.

  • create_product_variantswrite · needs approval

    Creates multiple product variants for a single product in one operation. You can run this mutation directly or as part of a bulk operation for large-scale catalog updates.

  • delete_product_variantswrite · needs approval

    Deletes multiple variants in a single `Product`. Specify the product ID and an array of variant IDs to remove variants in bulk. You can call this mutation directly or through the `bulkOperationRunMutation` mutation. Returns the updated product and any `UserError` objects.

  • reorder_product_variantswrite · needs approval

    Reorders multiple variants in a single product. This mutation can be called directly or via the bulkOperation.

  • update_product_variantswrite · needs approval

    Updates multiple product variants for a single product in one operation. You can run this mutation directly or as part of a bulk operation for large-scale catalog updates.

  • add_tagswrite · needs approval

    Adds tags to a resource. If the resource type doesn't support tagging, the `id` argument returns a resource-not-found error.

  • remove_tagswrite · needs approval

    Removes tags from a resource. If the resource type doesn't support tagging, the `id` argument returns a resource-not-found error.

  • get_collectionread-only

    Retrieves a collection by its ID. A collection represents a grouping of products that merchants can display and sell as a group in their online store and other sales channels.

  • get_collection_by_identifierread-only

    Return a collection by an identifier.

  • list_collectionsread-only

    Retrieves a list of collections in a store. Collections are groups of products that merchants can organize for display in their online store and other sales channels. For example, an athletics store might create different collections for running attire, shoes, and accessories. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_collectionsread-only

    Count of collections. Limited to a maximum of 10000 by default.

  • create_collectionwrite · needs approval

    Creates a collection to group products together in the online store and other sales channels. For example, an athletics store might create different collections for running attire, shoes, and accessories.

  • delete_collectionwrite · needs approval

    Deletes a collection and removes it permanently from the store. This operation cannot be undone and will remove the collection from all sales channels where it was published. Permanent. The products stay.

  • duplicate_collectionwrite · needs approval

    Duplicates a collection.

  • reorder_collection_productswrite · needs approval

    Asynchronously reorders products within a specified collection. Instead of returning an updated collection, this mutation returns a job, which should be polled. The `Collection.sortOrder` must be `MANUAL`.

  • update_collectionwrite · needs approval

    Updates a collection, modifying its properties, products, or publication settings. Collections help organize products together in the online store and other sales channels.

  • get_publicationread-only

    Retrieves a `Publication` by `ID`.

  • list_publicationsread-only

    Returns a paginated list of `Publication`. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • publish_resourcewrite · needs approval

    Publishes a resource, such as a `Product` or `Collection`, to one or more publications.

  • unpublish_resourcewrite · needs approval

    Unpublishes a resource, such as a `Product` or `Collection`, from one or more publications. The resource remains in your store but becomes unavailable to customers.

  • get_inventory_itemread-only

    Returns an InventoryItem object by ID.

  • list_inventory_itemsread-only

    Returns a list of inventory items. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_inventory_levelread-only

    Returns an InventoryLevel object by ID.

  • get_inventory_shipmentread-only

    Retrieves an `InventoryShipment` by ID. Returns tracking details, `InventoryShipmentLineItem` objects with quantities, and the shipment's current `InventoryShipmentStatus`.

  • list_inventory_shipmentsread-only

    Returns a paginated list of `InventoryShipment` objects. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_inventory_transferread-only

    Returns an `InventoryTransfer` by ID. Inventory transfers track the movement of inventory between locations, including origin and destination details, `InventoryTransferLineItem` objects, quantities, and `InventoryTransferStatus` values.

  • list_inventory_transfersread-only

    Returns a paginated list of `InventoryTransfer` objects between locations. Transfers track the movement of `InventoryItem` objects between `Location` objects. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • activate_inventory_at_locationwrite · needs approval

    Activates an inventory item at a `Location` by creating an `InventoryLevel` that tracks stock quantities. This enables you to manage inventory for a `ProductVariant` at the specified location.

  • adjust_inventorywrite · needs approval

    Adjusts quantities for inventory items by applying incremental changes at specific locations. Each adjustment modifies the quantity by a delta value rather than setting an absolute amount.

  • deactivate_inventory_at_locationwrite · needs approval

    Removes an inventory item's quantities from a location, and turns off inventory at the location.

  • update_inventory_itemwrite · needs approval

    Updates an `InventoryItem`'s properties including whether inventory is tracked, cost, SKU, and whether shipping is required. Inventory items represent the goods available to be shipped to customers.

  • move_inventorywrite · needs approval

    Moves inventory quantities for a single inventory item between different states at a single location. Use this mutation to reallocate inventory across quantity states without moving it between locations.

  • set_inventorywrite · needs approval

    Set quantities of specified name using absolute values. This mutation supports compare-and-set functionality to handle concurrent requests properly. If `ignoreCompareQuantity` is not set to true, the mutation will only update the quantity if the persisted quantity matches the `compareQuantity` value. If the `compareQuantity` value does not match the persisted value, the mutation will return an error.

  • create_inventory_shipmentwrite · needs approval

    Adds a draft shipment to an inventory transfer.

  • mark_inventory_shipment_in_transitwrite · needs approval

    Marks a draft inventory shipment as in transit.

  • receive_inventory_shipmentwrite · needs approval

    Receive an inventory shipment.

  • set_inventory_shipment_trackingwrite · needs approval

    Edits the tracking info on an inventory shipment.

  • cancel_inventory_transferwrite · needs approval

    Cancels an inventory transfer.

  • create_inventory_transferwrite · needs approval

    Creates a draft inventory transfer to move inventory items between `Location` objects in your store. The transfer tracks which items to move, their quantities, and the origin and destination locations.

  • mark_inventory_transfer_readywrite · needs approval

    Sets an inventory transfer to ready to ship.

  • set_inventory_transfer_itemswrite · needs approval

    This mutation sets the quantity for one or more line items on a Transfer.

  • get_delivery_profileread-only

    Retrieves a `DeliveryProfile` by ID. Delivery profiles group shipping settings for specific `Product` objects that ship from selected `Location` objects to delivery zones.

  • list_delivery_profilesread-only

    Returns a paginated list of `DeliveryProfile` objects for the shop. Delivery profiles group `Product` and `ProductVariant` objects that share shipping rates and zones. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_locationread-only

    Retrieves a `Location` by its ID. Locations are physical places where merchants store inventory, such as warehouses, retail stores, or fulfillment centers.

  • get_location_by_identifierread-only

    Return a location by an identifier.

  • list_locationsread-only

    A paginated list of inventory locations where merchants can stock `Product` items and fulfill `Order` items. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_locationsread-only

    Returns the count of locations for the given shop. Limited to a maximum of 10000 by default.

  • get_customerread-only

    Returns a `Customer` resource by ID.

  • get_customer_by_identifierread-only

    Return a customer by an identifier.

  • get_customer_merge_statusread-only

    Returns the status of a customer merge request job.

  • preview_customer_mergeread-only

    Returns a preview of a customer merge request.

  • list_segment_membersread-only

    A paginated list of customers that belong to an individual `Segment`. Segments group customers based on criteria defined through ShopifyQL queries. Access segment members with their profile information and purchase summary data. The connection includes statistics for analyzing segment attributes (such as average and sum calculations) and a total count of all members. The maximum page size is 1000. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_customersread-only

    Returns a list of customers in your Shopify store, including key information such as name, email, location, and purchase history. Use this query to segment your audience, personalize marketing campaigns, or analyze customer behavior by applying filters based on location, order history, marketing preferences and tags. The `customers` query supports pagination and sorting. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_customersread-only

    The number of customers. Limited to a maximum of 10000 by default.

  • get_segmentread-only

    Retrieves a customer `Segment` by ID. Segments are dynamic groups of customers that meet specific criteria defined through ShopifyQL queries.

  • list_segment_filtersread-only

    A list of filters. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_segmentsread-only

    Returns a paginated list of `Segment` objects for the shop. Segments are dynamic groups of customers that meet specific criteria defined through ShopifyQL queries. You can filter segments by search query and sort them by creation date or other criteria. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_segmentsread-only

    The number of segments for a shop. Limited to a maximum of 10000 by default.

  • get_store_credit_accountread-only

    Retrieves a `StoreCreditAccount` by ID. Store credit accounts hold monetary balances that account owners can use at checkout. The owner is either a `Customer` or a `CompanyLocation`.

  • create_customer_addresswrite · needs approval

    Creates a new `MailingAddress` for a `Customer`. You can optionally set the address as the customer's default address.

  • delete_customer_addresswrite · needs approval

    Deletes a customer's address.

  • update_customer_addresswrite · needs approval

    Updates a `Customer`'s `MailingAddress`. You can modify any field of the address and optionally set it as the customer's default address.

  • create_customerwrite · needs approval

    Creates a new `Customer` in the store.

  • delete_customerwrite · needs approval

    Deletes a `Customer` from the store. You can only delete customers who haven't placed any orders. Permanent. Shopify refuses it for a customer who has orders.

  • update_customer_email_consentwrite · needs approval

    Updates a `Customer`'s email marketing consent information. The customer must have an email address to update their consent. Records the marketing state (such as subscribed, pending, unsubscribed), opt-in level, and when and where the customer gave or withdrew consent. Record only consent the customer actually gave: it decides who receives marketing email.

  • merge_customerswrite · needs approval

    Merges two customers.

  • send_customer_account_invitewrite · needs approval

    Sends an email invitation for a customer to create a legacy customer account. The invitation lets customers set up their password and activate their account in the online store. Emails the customer.

  • update_customer_sms_consentwrite · needs approval

    Updates a customer's SMS marketing consent information. The customer must have a phone number on their account to receive SMS marketing. Record only consent the customer actually gave: it decides who receives marketing SMS.

  • update_customerwrite · needs approval

    Updates a `Customer`'s attributes including personal information and `tax exemptions`.

  • set_customer_default_addresswrite · needs approval

    Updates a customer's default address.

  • create_segmentwrite · needs approval

    Creates a segment.

  • delete_segmentwrite · needs approval

    Deletes a segment.

  • update_segmentwrite · needs approval

    Updates a segment.

  • credit_store_creditwrite · needs approval

    Adds funds to a `StoreCreditAccount` by creating a `StoreCreditAccountCreditTransaction`. The mutation accepts either a store credit account ID, a `Customer` ID, or a `CompanyLocation` ID. When you provide a customer or company location ID, it automatically creates an account if one doesn't exist for the specified currency. Adds store credit the customer can spend.

  • debit_store_creditwrite · needs approval

    Creates a debit transaction that decreases the store credit account balance by the given amount. Removes store credit from the customer.

  • list_companiesread-only

    A paginated list of companies in the shop. `Company` objects are business entities that purchase from the merchant. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_companiesread-only

    The number of companies for a shop. Limited to a maximum of 10000 by default.

  • get_companyread-only

    Returns a `Company` resource by ID.

  • get_company_contactread-only

    Returns a `CompanyContact` resource by ID.

  • get_company_locationread-only

    Returns a `CompanyLocation` resource by ID.

  • list_company_locationsread-only

    A paginated list of `CompanyLocation` objects for B2B customers. Company locations represent individual branches or offices of a `Company` where B2B orders can be placed. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • add_customer_to_companywrite · needs approval

    Adds an existing `Customer` as a contact to a `Company`. Companies are business entities that make purchases from the merchant's store. Use this mutation when you have a customer who needs to be associated with a B2B company to make purchases on behalf of that company.

  • assign_company_contact_rolewrite · needs approval

    Assigns a role to a contact for a location.

  • create_company_contactwrite · needs approval

    Creates a company contact and the associated customer.

  • update_company_contactwrite · needs approval

    Updates a company contact.

  • create_companywrite · needs approval

    Creates a `Company` for B2B commerce. This mutation creates the company and can optionally create an initial `CompanyContact` and `CompanyLocation` in a single operation. Company contacts are people who place orders on behalf of the company. Company locations are branches or offices with their own billing and shipping addresses.

  • create_company_locationwrite · needs approval

    Creates a new location for a `Company`. Company locations are branches or offices where B2B customers can place orders with specific pricing, catalogs, and payment terms.

  • update_company_locationwrite · needs approval

    Updates a company location's information and B2B checkout settings. Company locations are branches or offices where `CompanyContact` members place orders on behalf of the company. Contacts must be assigned to a location through `roleAssignments` to place orders.

  • update_companywrite · needs approval

    Updates a `Company` with new information. Companies represent business customers that can have multiple contacts and locations with specific pricing, payment terms, and checkout settings.

  • get_discount_by_coderead-only

    Retrieves a code discount by its discount code. The search is case-insensitive, enabling you to find discounts regardless of how customers enter the code.

  • count_discount_codesread-only

    The total number of discount codes for the shop. Limited to a maximum of 10000 by default.

  • get_discountread-only

    Returns a `DiscountNode` resource by ID.

  • list_discountsread-only

    Returns a list of discounts. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_discountsread-only

    The total number of discounts for the shop. Limited to a maximum of 10000 by default.

  • activate_automatic_discountwrite · needs approval

    Activates an automatic discount.

  • create_automatic_discountwrite · needs approval

    Creates an amount off discount that's automatically applied on a cart and at checkout.

  • update_automatic_discountwrite · needs approval

    Updates an existing amount off discount that's automatically applied on a cart and at checkout.

  • create_bxgy_automatic_discountwrite · needs approval

    Creates a buy X get Y discount (BXGY) that's automatically applied on a cart and at checkout.

  • update_bxgy_automatic_discountwrite · needs approval

    Updates an existing buy X get Y discount (BXGY) that's automatically applied on a cart and at checkout.

  • deactivate_automatic_discountwrite · needs approval

    Deactivates an automatic discount.

  • delete_automatic_discountwrite · needs approval

    Deletes an existing automatic discount from the store, permanently removing it from all future order calculations. This mutation provides a clean way to remove promotional campaigns that are no longer needed.

  • create_free_shipping_automatic_discountwrite · needs approval

    Creates automatic free shipping discounts that apply to qualifying orders without requiring discount codes. These promotions automatically activate when customers meet specified criteria, streamlining the checkout experience.

  • update_free_shipping_automatic_discountwrite · needs approval

    Updates existing automatic free shipping discounts, allowing merchants to modify promotion criteria, shipping destinations, and eligibility requirements without recreating the entire discount structure.

  • activate_code_discountwrite · needs approval

    Activates a previously created code discount, making it available for customers to use during checkout. This mutation transitions inactive discount codes into an active state where they can be applied to orders.

  • create_code_discountwrite · needs approval

    Creates an amount off discount that's applied on a cart and at checkout when a customer enters a code. Amount off discounts can be a percentage off or a fixed amount off.

  • update_code_discountwrite · needs approval

    Updates an amount off discount that's applied on a cart and at checkout when a customer enters a code. Amount off discounts can be a percentage off or a fixed amount off.

  • bulk_activate_discount_codeswrite · needs approval

    Activates multiple code discounts asynchronously using one of the following: - A search query - A saved search ID - A list of discount code IDs

  • bulk_deactivate_discount_codeswrite · needs approval

    Deactivates multiple code-based discounts asynchronously using one of the following: - A search query - A saved search ID - A list of discount code IDs

  • create_bxgy_code_discountwrite · needs approval

    Creates a buy X get Y discount (BXGY) that's applied on a cart and at checkout when a customer enters a code.

  • update_bxgy_code_discountwrite · needs approval

    Updates a buy X get Y discount (BXGY) that's applied on a cart and at checkout when a customer enters a code.

  • deactivate_code_discountwrite · needs approval

    Temporarily suspends a code discount without permanently removing it from the store. Deactivation allows merchants to pause promotional campaigns while preserving the discount configuration for potential future use.

  • delete_code_discountwrite · needs approval

    Removes a code discount from the store, making it permanently unavailable for customer use. This mutation provides a clean way to eliminate discount codes that are no longer needed or have been replaced.

  • create_free_shipping_code_discountwrite · needs approval

    Creates an free shipping discount that's applied on a cart and at checkout when a customer enters a code.

  • update_free_shipping_code_discountwrite · needs approval

    Updates a free shipping discount that's applied on a cart and at checkout when a customer enters a code.

  • delete_discount_codeswrite · needs approval

    Asynchronously delete discount codes in bulk that customers can use to redeem a discount.

  • add_discount_codeswrite · needs approval

    Asynchronously add discount codes in bulk that customers can use to redeem a discount. You can use the `discountRedeemCodeBulkAdd` mutation to automate the distribution of discount codes through emails or other marketing channels.

  • get_gift_cardread-only

    Retrieves a `GiftCard` by its ID. Returns the gift card's balance, transaction history, `Customer` information, and whether it's enabled.

  • list_gift_cardsread-only

    Returns a paginated list of `GiftCard` objects issued for the shop. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_gift_cardsread-only

    Returns the total count of gift cards that have been issued by the shop. Use this for dashboard summaries or to understand the scale of a merchant's gift card program. The count includes all gift cards regardless of status (active, disabled, or fully redeemed). Limited to a maximum of 10000 by default.

  • create_gift_cardwrite · needs approval

    Creates a new `GiftCard` with a specified initial value. You can assign the gift card to a `Customer` or create it without assignment for manual distribution.

  • credit_gift_cardwrite · needs approval

    Adds funds to an existing gift card, increasing its available balance. Use this when a merchant wants to top up a customer's gift card — for example, as a promotional bonus, a customer service gesture, or to reload a reusable gift card. Adds spendable value to the gift card.

  • deactivate_gift_cardwrite · needs approval

    Deactivate a gift card. A deactivated gift card cannot be used by a customer. A deactivated gift card cannot be re-enabled.

  • debit_gift_cardwrite · needs approval

    Removes funds from a gift card, decreasing its available balance. Use this for manual balance adjustments — for example, correcting an accidental over-credit or applying a fee. Removes spendable value from the gift card.

  • send_gift_card_to_customerwrite · needs approval

    Sends a notification to the customer who purchased a gift card, including the gift card details and code. The notification is delivered using the customer's available contact method. Use this to resend the purchase confirmation or remind the purchaser about a gift card they bought. Emails the customer.

  • send_gift_card_to_recipientwrite · needs approval

    Sends a notification to the designated recipient of a gift card, delivering the gift card code and redemption instructions. The notification is delivered using the recipient's available contact method. Use this to deliver or re-deliver the gift card to the intended recipient. Emails the gift card's recipient.

  • update_gift_cardwrite · needs approval

    Updates the properties of an existing gift card, such as its expiration date, note, or template suffix. Use this to modify gift card details — for example, extending an expiration date for a loyal customer or adding an internal note for tracking purposes.

  • list_marketing_activitiesread-only

    A list of marketing activities associated with the marketing app. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_marketing_activityread-only

    Returns a `MarketingActivity` resource by ID.

  • get_marketing_eventread-only

    Returns a `MarketingEvent` resource by ID.

  • list_marketing_eventsread-only

    A list of marketing events associated with the marketing app. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • run_shopifyql_queryread-only

    Executes a ShopifyQL query to analyze store data and returns results in a tabular format. ShopifyQL, e.g. FROM sales SHOW total_sales BY month SINCE -12m. Tabular result.

  • get_articleread-only

    Returns a `Article` resource by ID.

  • list_article_authorsread-only

    List of article authors for the shop. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_article_tagsread-only

    List of all article tags.

  • list_articlesread-only

    Returns a paginated list of articles from the shop's blogs. `Article` objects are blog posts that contain content like text, images, and tags. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_blogread-only

    Returns a `Blog` resource by ID.

  • list_blogsread-only

    Returns a paginated list of the shop's `Blog` objects. Blogs serve as containers for `Article` objects and provide content management capabilities for the store's editorial content. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_blogsread-only

    Count of blogs. Limited to a maximum of 10000 by default.

  • get_commentread-only

    Returns a `Comment` resource by ID.

  • list_commentsread-only

    List of the shop's comments. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_menuread-only

    Returns a `Menu` resource by ID.

  • list_menusread-only

    Retrieves navigation menus. Menus organize content into hierarchical navigation structures that merchants can display in the online store (for example, in headers, footers, and sidebars) and customer accounts. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_pageread-only

    Returns a `Page` resource by ID.

  • list_pagesread-only

    A paginated list of pages from the online store. `Page` objects are content pages that merchants create to provide information to customers, such as "About Us", "Contact", or policy pages. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_pagesread-only

    Count of pages. Limited to a maximum of 10000 by default.

  • get_url_redirectread-only

    Returns a `UrlRedirect` resource by ID.

  • list_url_redirectsread-only

    A list of redirects for a shop. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_url_redirectsread-only

    Count of redirects. Limited to a maximum of 10000 by default.

  • create_articlewrite · needs approval

    Creates an `Article`. Articles are content pieces that include a title, body text, and author information.

  • delete_articlewrite · needs approval

    Permanently deletes a blog article from a shop's blog. This mutation removes the article and all associated metadata.

  • update_articlewrite · needs approval

    Updates an existing `Article`. You can modify the article's content, metadata, publication status, and associated properties like author information and tags.

  • create_blogwrite · needs approval

    Creates a new blog within a shop, establishing a container for organizing articles.

  • delete_blogwrite · needs approval

    Permanently deletes a blog from a shop. This mutation removes the blog container and its organizational structure.

  • update_blogwrite · needs approval

    Updates an existing blog's configuration and settings. This mutation allows merchants to modify blog properties to keep their content strategy current.

  • approve_commentwrite · needs approval

    Approves a pending comment, making it visible to store visitors on the associated blog article.

  • delete_commentwrite · needs approval

    Permanently removes a comment from a blog article.

  • mark_comment_not_spamwrite · needs approval

    Reverses a spam classification on a comment, restoring it to normal moderation status. This mutation allows merchants to change their decision when a comment has been manually marked as spam.

  • mark_comment_spamwrite · needs approval

    Marks a comment as spam, removing it from public view. This mutation enables merchants to quickly handle unwanted promotional content, malicious links, or other spam that appears in blog discussions.

  • create_menuwrite · needs approval

    Creates a navigation `Menu` for the online store. Menus organize links that help customers navigate to collections, products, pages, blogs, and custom URLs.

  • delete_menuwrite · needs approval

    Deletes a menu.

  • update_menuwrite · needs approval

    Updates a `Menu` for display on the storefront. Modifies the menu's title and navigation structure, including nested `MenuItem` objects. You can update the handle for non-default menus.

  • create_pagewrite · needs approval

    Creates a `Page` for the online store.

  • delete_pagewrite · needs approval

    Permanently deletes a page from the online store.

  • update_pagewrite · needs approval

    Updates an existing page's content and settings.

  • create_url_redirectwrite · needs approval

    Creates a `UrlRedirect` object.

  • delete_url_redirectwrite · needs approval

    Deletes a `UrlRedirect` object.

  • update_url_redirectwrite · needs approval

    Updates a URL redirect.

  • list_filesread-only

    Retrieves a paginated list of files that have been uploaded to a Shopify store. Files represent digital assets that merchants can upload to their store for various purposes including product images, marketing materials, documents, and brand assets. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • create_filewrite · needs approval

    Creates file assets for a store from external URLs or files that were previously uploaded using the `stagedUploadsCreate` mutation.

  • delete_filewrite · needs approval

    Deletes file assets that were previously uploaded to your store.

  • update_filewrite · needs approval

    Updates properties, content, and metadata associated with an existing file asset that has already been uploaded to Shopify.

  • get_themeread-only

    Returns an `OnlineStoreTheme` by its ID. Use this query to retrieve theme metadata and access the theme's `files`, which include templates, assets, translations, and configuration files.

  • list_themesread-only

    Returns a paginated list of `OnlineStoreTheme` objects for the online store. Themes control the appearance and layout of the storefront. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_shop_localesread-only

    Returns the locales enabled on a shop. Each locale represents a language for translations and determines how content displays to customers in different markets.

  • get_translatable_resourceread-only

    Retrieves a resource that has translatable fields. Returns the resource's `Translation` objects for different locales and markets, along with the original `TranslatableContent` and digest values needed to register new translations.

  • list_translatable_resourcesread-only

    Returns a paginated list of `TranslatableResource` objects for a specific resource type. Each resource provides translatable content and digest values needed for the `translationsRegister` mutation. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_translatable_resources_by_idsread-only

    Returns a paginated list of `TranslatableResource` objects for the specified resource IDs. Each resource provides translatable content and digest values needed for the `translationsRegister` mutation. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • register_translationswrite · needs approval

    Creates or updates translations for a resource's translatable content.

  • remove_translationswrite · needs approval

    Deletes translations.

  • get_metafield_definitionread-only

    Retrieves a `MetafieldDefinition` by its identifier. You can identify a definition using either its owner type, namespace, and key, or its global ID.

  • list_metafield_definitionsread-only

    Returns a list of metafield definitions. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_metaobjectread-only

    Retrieves a single `Metaobject` by its global ID. Metaobjects store custom structured data based on defined schemas. The returned metaobject includes its fields with values, display name, handle, and associated metadata like update timestamps and capabilities.

  • get_metaobject_by_handleread-only

    Retrieves a `Metaobject` by its handle and type. Handles are unique identifiers within a metaobject type.

  • get_metaobject_definitionread-only

    Retrieves a `MetaobjectDefinition` by its global ID. Metaobject definitions provide the structure and fields for metaobjects.

  • get_metaobject_definition_by_typeread-only

    Retrieves a `MetaobjectDefinition` by its type. The type serves as a unique identifier that distinguishes one metaobject definition from another.

  • list_metaobject_definitionsread-only

    Returns a paginated list of all `MetaobjectDefinition` objects configured for the store. Metaobject definitions provide the schema for creating custom data structures composed of individual fields. Each definition specifies the field types, access permissions, and capabilities for `Metaobject` entries of that type. Use this query to discover available metaobject types before creating or querying metaobject entries. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • list_metaobjectsread-only

    Returns a paginated list of `Metaobject` entries for a specific type. Metaobjects are custom data structures that extend Shopify's data model with merchant or app-specific data types. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • delete_metafieldswrite · needs approval

    Deletes `Metafield` objects in bulk by specifying combinations of owner ID, namespace, and key.

  • set_metafieldswrite · needs approval

    Sets metafield values. Metafield values will be set regardless if they were previously created or not.

  • create_metaobjectwrite · needs approval

    Creates a metaobject entry based on an existing `MetaobjectDefinition`. The type must match a definition that already exists in the shop.

  • delete_metaobjectwrite · needs approval

    Deletes the specified metaobject and its associated metafields.

  • update_metaobjectwrite · needs approval

    Updates a `Metaobject` with new field values, handle, or capabilities. Metaobjects are custom data structures that extend Shopify's data model.

  • upsert_metaobjectwrite · needs approval

    Creates or updates a `Metaobject` based on its handle. If a metaobject with the specified handle exists, the mutation updates it with the provided field values. If no matching metaobject exists, the mutation creates a new one.

  • get_marketread-only

    Returns a `Market` resource by ID.

  • list_marketsread-only

    Returns a paginated list of `Market` objects configured for the shop. Markets match buyers based on defined conditions to deliver customized shopping experiences. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_price_listread-only

    Returns a `PriceList` by ID. You can use price lists to specify either fixed prices or adjusted relative prices that override initial `Product` prices.

  • list_price_listsread-only

    All price lists for a shop. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_disputeread-only

    Returns a `ShopifyPaymentsDispute` resource by ID.

  • list_disputesread-only

    Returns a paginated list of all Shopify Payments disputes for the shop. Disputes occur when a buyer files a complaint with their payments provider, and the merchant must provide evidence to contest it. Each dispute includes the status, amount, reason, and associated order. Use this to monitor and manage open chargebacks and track dispute resolution outcomes. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • get_shopify_payments_accountread-only

    Returns the Shopify Payments account information for the shop. Includes current balances across all currencies, payout schedules, and bank account configurations.

  • get_eventread-only

    Retrieves a single event by ID. Events chronicle activities in your store such as resource creation, updates, or staff comments. The query returns an `Event` interface of type `BasicEvent` or `CommentEvent`.

  • list_eventsread-only

    A paginated list of events that chronicle activities in the store. `Event` is an interface implemented by types such as `BasicEvent` and `CommentEvent` that track actions such as creating `Article` objects, fulfilling `Order` objects, adding `Product` objects, or staff comments on timelines. Returns one page: pass pageInfo.endCursor as `after` for the next.

  • count_eventsread-only

    Count of events. Limited to a maximum of 10000.

  • get_jobread-only

    Returns a Job resource by ID. Used to check the status of internal jobs and any applicable changes.

  • get_shopread-only

    Returns the Shop resource corresponding to the access token used in the request. The Shop resource contains business and store management settings for the shop.

Example prompts

Just ask your AI in plain language — it picks the right Shopify tool:

  • Returns a list of abandoned checkouts. A checkout is considered abandoned when a customer adds contact information but doesn't complete their purchase. Includes both abandoned and recovered checkouts. Returns one page: pass pageInfo.endCursor as `after` for the next — from Shopify, in plain language.
  • Returns the count of abandoned checkouts for the given shop. Limited to a maximum of 10000 by default — from Shopify, in plain language.
  • The `order` query retrieves an order by its ID. This query provides access to comprehensive order information such as customer details, line items, financial data, and fulfillment status — from Shopify, in plain language.
  • Return an order by an identifier — from Shopify, in plain language.

How it works

  1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
  2. Connect Shopify with a secure OAuth connection — each user connects their own account, credentials encrypted at rest.
  3. Your AI instantly gets the Shopify tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Shopify have an official MCP server?
You don't need one. Proxoria exposes Shopify to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Shopify MCP server required.
What can my AI do with Shopify through Proxoria?
It gets 307 tools: list_abandoned_checkouts, count_abandoned_checkouts, get_order, get_order_by_identifier, get_order_payment_status, list_orders, count_orders, count_pending_orders, get_refund, list_tender_transactions, cancel_order, capture_payment, close_order, remove_order_customer, set_order_customer, send_order_invoice, mark_order_as_paid, open_order, update_order, send_payment_reminder, refund_order, edit_order, get_draft_order, list_draft_order_delivery_options, get_draft_order_tag, list_draft_orders, count_draft_orders, add_draft_order_tags, remove_draft_order_tags, calculate_draft_order, complete_draft_order, create_draft_order, create_draft_order_from_order, delete_draft_order, duplicate_draft_order, preview_draft_order_invoice, send_draft_order_invoice, update_draft_order, get_fulfillment, get_fulfillment_order, list_fulfillment_orders, list_held_fulfillment_orders, cancel_fulfillment, create_fulfillment, create_fulfillment_event, cancel_fulfillment_order, hold_fulfillment_order, mark_ready_for_pickup, merge_fulfillment_order, move_fulfillment_order, release_fulfillment_order_hold, reschedule_fulfillment_order, split_fulfillment_order, set_fulfillment_deadline, update_fulfillment_tracking, get_return, calculate_return, list_return_reasons, get_returnable_fulfillment, list_returnable_fulfillments, get_reverse_delivery, get_reverse_fulfillment_order, remove_from_return, approve_return_request, cancel_return, close_return, create_return, decline_return_request, process_return, reopen_return, request_return, create_reverse_delivery, update_reverse_delivery_shipping, dispose_returned_items, get_product, get_product_by_identifier, get_product_duplicate_job, get_product_operation, list_product_tags, list_product_types, get_product_variant, get_product_variant_by_identifier, list_product_variants, count_product_variants, list_product_vendors, list_products, count_products, get_selling_plan_group, list_selling_plan_groups, search_product_taxonomy, create_product_bundle, update_product_bundle, create_product, delete_product, duplicate_product, update_product_option, create_product_options, delete_product_options, reorder_product_options, reorder_product_media, update_product, attach_variant_media, detach_variant_media, create_product_variants, delete_product_variants, reorder_product_variants, update_product_variants, add_tags, remove_tags, get_collection, get_collection_by_identifier, list_collections, count_collections, create_collection, delete_collection, duplicate_collection, reorder_collection_products, update_collection, get_publication, list_publications, publish_resource, unpublish_resource, get_inventory_item, list_inventory_items, get_inventory_level, get_inventory_shipment, list_inventory_shipments, get_inventory_transfer, list_inventory_transfers, activate_inventory_at_location, adjust_inventory, deactivate_inventory_at_location, update_inventory_item, move_inventory, set_inventory, create_inventory_shipment, mark_inventory_shipment_in_transit, receive_inventory_shipment, set_inventory_shipment_tracking, cancel_inventory_transfer, create_inventory_transfer, mark_inventory_transfer_ready, set_inventory_transfer_items, get_delivery_profile, list_delivery_profiles, get_location, get_location_by_identifier, list_locations, count_locations, get_customer, get_customer_by_identifier, get_customer_merge_status, preview_customer_merge, list_segment_members, list_customers, count_customers, get_segment, list_segment_filters, list_segments, count_segments, get_store_credit_account, create_customer_address, delete_customer_address, update_customer_address, create_customer, delete_customer, update_customer_email_consent, merge_customers, send_customer_account_invite, update_customer_sms_consent, update_customer, set_customer_default_address, create_segment, delete_segment, update_segment, credit_store_credit, debit_store_credit, list_companies, count_companies, get_company, get_company_contact, get_company_location, list_company_locations, add_customer_to_company, assign_company_contact_role, create_company_contact, update_company_contact, create_company, create_company_location, update_company_location, update_company, get_discount_by_code, count_discount_codes, get_discount, list_discounts, count_discounts, activate_automatic_discount, create_automatic_discount, update_automatic_discount, create_bxgy_automatic_discount, update_bxgy_automatic_discount, deactivate_automatic_discount, delete_automatic_discount, create_free_shipping_automatic_discount, update_free_shipping_automatic_discount, activate_code_discount, create_code_discount, update_code_discount, bulk_activate_discount_codes, bulk_deactivate_discount_codes, create_bxgy_code_discount, update_bxgy_code_discount, deactivate_code_discount, delete_code_discount, create_free_shipping_code_discount, update_free_shipping_code_discount, delete_discount_codes, add_discount_codes, get_gift_card, list_gift_cards, count_gift_cards, create_gift_card, credit_gift_card, deactivate_gift_card, debit_gift_card, send_gift_card_to_customer, send_gift_card_to_recipient, update_gift_card, list_marketing_activities, get_marketing_activity, get_marketing_event, list_marketing_events, run_shopifyql_query, get_article, list_article_authors, list_article_tags, list_articles, get_blog, list_blogs, count_blogs, get_comment, list_comments, get_menu, list_menus, get_page, list_pages, count_pages, get_url_redirect, list_url_redirects, count_url_redirects, create_article, delete_article, update_article, create_blog, delete_blog, update_blog, approve_comment, delete_comment, mark_comment_not_spam, mark_comment_spam, create_menu, delete_menu, update_menu, create_page, delete_page, update_page, create_url_redirect, delete_url_redirect, update_url_redirect, list_files, create_file, delete_file, update_file, get_theme, list_themes, list_shop_locales, get_translatable_resource, list_translatable_resources, get_translatable_resources_by_ids, register_translations, remove_translations, get_metafield_definition, list_metafield_definitions, get_metaobject, get_metaobject_by_handle, get_metaobject_definition, get_metaobject_definition_by_type, list_metaobject_definitions, list_metaobjects, delete_metafields, set_metafields, create_metaobject, delete_metaobject, update_metaobject, upsert_metaobject, get_market, list_markets, get_price_list, list_price_lists, get_dispute, list_disputes, get_shopify_payments_account, get_event, list_events, count_events, get_job, get_shop. For example, returns a list of abandoned checkouts. a checkout is considered abandoned when a customer adds contact information but doesn't complete their purchase. includes both abandoned and recovered checkouts. returns one page: pass pageinfo.endcursor as `after` for the next.
Is the Shopify connector read-only?
No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Shopify.
How do I connect Shopify to my AI?
Create a Proxoria account, connect Shopify with a secure OAuth connection, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Shopify tools.

Ready to connect Shopify to your AI?

Set it up in minutes — no code, secure by default.

Get started free

About Proxoria. Proxoria connects AI assistants — Claude, ChatGPT, Mistral and any Model Context Protocol (MCP) client — to the business apps you already use, turning each app's API into tools your AI can call, with per-user authentication and write actions gated by human approval.