Connect an AI assistant

A connector lets an AI assistant work in one Tringify store, or one developer organization, on your behalf. Tringify hosts the MCP server: you don't run a server, install a Tringify package or create an API key. You sign in to Tringify, choose the store or organization, and approve the access the assistant asks for. It can then do only what you approved and what your own role allows, and every change it makes is recorded under your name and the tool's name.

Use the Store URL unless you build themes. The same URLs work for every store; you never pick a different address. Each connection reaches one store or one organization; to work in two, add the server twice under different names and approve each one.

The approval screen shows the domain the tool came from and says when Tringify hasn't verified the tool's name. Desktop and command-line assistants finish sign-in through a callback on your own computer, so complete it in a browser on the same computer.

claude.ai and Claude Desktop: open Settings → Connectors, choose Add custom connector, name it Tringify and enter the Store URL. Select Connect and approve access in the browser. A connector added to your Claude account is available in claude.ai and in Claude Desktop. On Claude Team and Enterprise plans, an owner may need to add the custom connector for the organization first.

Claude Code: add the server, then run /mcp in Claude Code, select tringify and authenticate.

Custom connectors need ChatGPT's developer mode, which depends on your ChatGPT plan. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. Back in Apps & Connectors, choose Create, name it Tringify, enter the Store URL, choose OAuth as the authentication and create it; ChatGPT opens Tringify's sign-in page. In a chat, turn the Tringify connector on from the developer mode tools menu.

Cursor's built-in sign-in returns to a cursor:// address. Tringify accepts sign-in callbacks only on HTTPS addresses or on your own computer, so connect Cursor through mcp-remote, an open-source bridge that signs in through a callback on your computer and needs Node.js. Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project), merging it into any servers already there, then open Cursor Settings → MCP and turn Tringify on. Your browser opens Tringify's sign-in page.

In the Codex app, open Settings → MCP servers → Add server. Name it Tringify, choose Streamable HTTP, and enter the Store URL. Save and restart when prompted, then select Authenticate.

With the Codex CLI, add the server with the command below and follow its sign-in prompt; if it still needs authentication, run codex mcp login tringify. The app and CLI share MCP settings on the same computer, so use either. See the connection guide and the GitHub quickstart for examples and troubleshooting.

Start a new conversation and ask the assistant to list five tags in the connected store. That read needs product read access; creating, renaming or deleting a tag also needs product write access. Try changes on a development store first. When a tool reports an uncertain result, ask the assistant to read the record back before trying again.

Some changes ask for the same verification code Store Admin asks for: removing a domain, setting up DNS with Tringify, changing DNS records, choosing or clearing the primary domain, unassigning a domain, and changing sending domains, sender addresses, the reply-to address or MAIL FROM. When you ask the assistant for one of them, it asks Tringify to email a code to the address on your Tringify account. Tringify never shows the code to the assistant. Read the code from the email and give it to the assistant; it works once, only for that change, and expires soon after it is sent. If you did not ask for the change, don't share the code. A passkey can't be used here: assistants and API tokens get the code by email only. Every code request is recorded in the store's activity log.

To give an assistant more or less access, sign in again from the assistant: in claude.ai or Claude Desktop, reconnect the connector; in Claude Code, run /mcp and authenticate again; in ChatGPT, reconnect from the connector's settings; in Cursor, turn the server off and on; in Codex, run codex mcp login tringify. On Tringify's approval screen, choose the existing connection and select Update access. Refreshing a connection never adds access.

Disconnect a tool in Accounts → Connected tools. Store and developer organization owners can disconnect their team's connections there too. Removing someone from the team ends their connections at once.

A connected assistant shares the store's Store API budget with the store's apps, and each connection also has a limit of its own, set by the store's plan; development and transfer stores have a smaller one. When the assistant goes over it, the tool call fails with RATE_LIMITED and says how many seconds to wait. See Rate limits.

Building your own MCP client, or need the exact scopes, limits and errors? See the Connector OAuth and MCP reference.

Payment tool results describe Tringify records. For Razorpay, all five provider operations are declared: charge, status, cancel, refund and refund_status. A browser return or Razorpay notification asks the platform to check the provider and cannot establish payment by itself. Use payment and refund records from the Store API tools and never invent a completed refund from a pending result. See Razorpay payment behavior.