Tringify MCP
Your AI assistant, working in your store.
Connect Claude, ChatGPT, Cursor or Codex to your Tringify store through MCP. You sign in, choose the store and approve the access it gets. It can then work with your catalog, content, themes and Markets, within what you allowed.
Add one URL to the assistant you use
Tringify hosts the MCP server. You don’t run a server, install a Tringify package or create an API key: add the Store server URL to your assistant, sign in to Tringify in your browser and approve. In a new conversation, the assistant lists Tringify’s tools for that store.
- Hosted by Tringify
- One server URL for every store. Nothing to install, and no API key to create, copy or store.
- The assistant you already use
- Claude, ChatGPT, Cursor and Codex connect with the steps in the docs. Other MCP clients can use the same server with OAuth and PKCE.
- The conversation stays in your assistant
- You ask in Claude, ChatGPT, Cursor or Codex. Tringify provides the server and its tools; your assistant calls them and shows you what came back.
- One store per connection
- A connection reaches the store you choose when you approve it. To work in two stores, add the server twice under different names and approve each one.
- A server for theme developers
- The Developer server works with a developer organization instead of a store: upload a theme bundle, publish a version and install it into a development store.
- Sign-in finishes on your computer
- Desktop and command-line assistants complete sign-in through a callback on your own computer, so approve in a browser on the same computer.
Access you choose, store by store
When your assistant connects, Tringify’s approval screen opens in your browser. Choose the store, review the access the assistant asks for and approve. Your password stays with Tringify, and the connection can do only what you approved and what your own role allows.
- Reading and changing are separate
- Viewing products and editing them are different permissions, and so are pages, blog, themes, Markets and orders. Approve only what the task needs.
- Your role still applies
- A connection never goes beyond your own permissions in that store. A staff member’s connection acts as that staff member, and a permission they lose leaves the connection too.
- Know which tool is asking
- Tringify’s own tools, such as the Tringify CLI, show Verified by Tringify. Other tools show the name they provided and their domain, or This computer for local tools.
- Change access later
- Sign in again from the assistant, choose the existing connection and select Update access. It keeps working until the update completes. Refreshing never adds access.
- Disconnect at any time
- Connected tools in your Tringify account lists every connection. Store owners can disconnect their team’s connections, and removing someone from the team ends theirs at once.
- Credentials of its own
- The assistant gets its own short-lived tokens, never your password or a Store API token. Access tokens last up to 15 minutes, and a connection expires after 90 days.
Tools for your whole store
Store tools run the matching Store API operations, with the same validation and limits. Your assistant receives only the tools your connection allows, so a read-only connection lists nothing that can change your store.
- Catalog
- Products and variants, collections and their rules, categories, attributes, tags, brands, vendors and metafields, with translations.
- Content
- Pages, policies, blog posts, tags, categories and authors, menus, and the SEO of storefront and listing pages.
- Online store and themes
- Storefronts, URL redirects, search settings and pixels. Theme code edits pass the code editor’s checks, and the live theme is refused unless explicitly allowed.
- Markets
- All 107 documented Markets operations: countries and currencies, tax, duties, shipping, discounts, cash on delivery, payment availability and checkout.
- Languages and currencies
- Enable languages and choose the default, translate content, add currencies and set rounding and exchange rates.
- Orders and customers
- Preview an order edit, review totals and refunds, then apply it. Customers, customer groups, store credit and email subscribers.
- Files
- Upload to Media or Site Assets, rename files and edit alt text. An upload is validated before it can be used.
- Domains and email
- Domains and DNS, sending domains, sender addresses and reply-to. These changes need a verification code that Tringify emails to you, never to the assistant.
- The same webhooks as Store Admin
- Changes made through MCP send the usual webhook events and audit entries, so apps and automations see them like any other change.
Every change is yours to approve
Your assistant acts as you, with the access you gave it. Tringify asks before anything destructive, records who made each change and limits how fast a connection can work.
- Confirmation before it’s gone
- Deleting, removing a language or taking a storefront offline first returns the impact and a single-use confirmation. Nothing changes until you approve.
- Recorded under your name
- The store’s activity log shows your account, API as the source and Connected tool with the tool’s name, such as Codex. Reading data adds no change entries.
- Verification codes stay with you
- Domain, DNS and email-sender changes ask for the code Store Admin asks for. Tringify emails it to you; you decide whether to give it to the assistant.
- Fair use of your store’s API
- A connection shares the store’s Store API budget with its apps and has its own limit set by your plan. Over it, a call says how many seconds to wait.
- Start with a read
- Ask for something that changes nothing first, try changes on a development store, and have the assistant read a record back when a result is uncertain.
- Disconnecting ends access
- A disconnected tool loses access. Work already under way may finish and completed changes aren’t reversed, so review changes as your assistant makes them.
Connect your assistant to your store.
The setup guide takes you through the connection step by step. The docs cover Claude, ChatGPT and Cursor, with every tool and the access it needs.
