Guide

Connect Zylx to your AI assistant

Zylx builds a Business Brain from your website and the tools you connect. Once you connect an AI assistant to it, that assistant answers from your real business instead of guessing. This page is the whole journey — for ChatGPT, Claude, Claude Code and Codex — and exactly what the assistant can and cannot do afterwards.

The journey, in six steps

  1. 1

    Find or install Zylx in your assistant

    In ChatGPT, that means the Zylx Studio plugin (see ChatGPT below for where it lives today). In Claude it is a connector; in Claude Code and Codex it is one command. Nothing happens to your data at this step.
  2. 2

    Connect

    Choose Connect in the assistant. It opens a Zylx sign-in in your browser — there is no key, token or configuration file to copy.
  3. 3

    Sign in to Zylx

    Use your normal Zylx account. If you are already signed in, you go straight to the approval screen.
  4. 4

    Choose businesses

    The approval screen lists every business your account can open right now. All current businesses are pre-selected; uncheck any you do not want; businesses added later are never included automatically.
  5. 5

    Approve

    Confirm. Zylx records exactly which businesses this one connection may reach; the assistant is told only that it is connected.
  6. 6

    Ready

    Ask something real: “What changed in my business this week?” or “Why are sales down?”. The assistant reads your Business Brain through Zylx.

What the approval screen shows

  • Which assistant is asking (for example ChatGPT, Claude Code) and the Zylx account it will be tied to.
  • Every business you can currently open, with your role in each (owner or member). Businesses you cannot open are not listed and cannot be added.
  • A checkbox per business. Select all means the businesses that exist right now — it is a snapshot, not a rule. A business created or shared with you tomorrow is never added to today's connection automatically; you add it yourself from the Servers page.
  • Whether the connection is read-only or may also propose changes. A read-only connection can never write anything to your businesses.

Where to find Zylx in each assistant

ChatGPT

Once Zylx Studio is listed: open the Plugins directory in ChatGPT, search for Zylx Studio and choose Connect. Then follow the six steps above.

Until then: in ChatGPT on the web, open Settings → Security and login and turn on Developer mode (on Business, Enterprise and Edu a workspace admin or owner has to do this). Open the Plugins page, choose the + button, name it Zylx Studio and paste the Zylx server address shown on your Servers page. Choose the sign-in option, approve on the Zylx screen, then let ChatGPT scan the tools. Developer mode is web-only, and it is not available on every plan — see plan compatibility.

Developer mode is web-only and availability varies by plan and workspace policy: Pro, Plus, Business, Enterprise and Edu are listed as eligible. Full MCP including write actions is currently a Business, Enterprise and Edu web beta that a workspace admin or owner must enable; Pro is read/fetch only. Free and Go are not listed for custom MCP.

Claude

On claude.ai or Claude Desktop: Settings → Connectors → Add custom connector. Paste the Zylx server address from your Servers page and approve the Zylx sign-in when it opens.

Ready on Claude plans that include custom connectors; Free accounts are limited to one connector. Team and Enterprise may require an owner to add it first.

Claude Code

One command adds Zylx (it is shown on your Servers page). Run /mcp, choose Zylx Studio → Authenticate, and approve in the browser.

Ready in Claude Code with remote HTTP MCP and automatic OAuth/DCR. The browser sign-in returns to a local loopback callback.

Codex

Add Zylx as a remote server from Codex's settings or with the command on your Servers page, then sign in. Desktop, CLI and the IDE extension share the same connection.

Ready in current Codex clients with remote HTTP MCP and OAuth. Desktop, CLI, and IDE share the same MCP configuration.

Add or remove businesses, or revoke a connection

  • Everything lives on one page: zylx.studio/servers.
  • Manage businesses adds or removes businesses for a connection you keep. Removing one takes effect on the assistant's next request.
  • Disconnect ends the connection immediately. Its tokens stop working and cannot be refreshed back to life. You can also remove Zylx from the assistant's own settings.
  • Changing who owns or belongs to a business in Zylx never widens an existing connection. Only the approval screen and Manage businesses can add a business.

What your assistant can and cannot do

It can

  • Read your Business Brain: what your business is, how it is doing, what changed, why, and what to do next — with the evidence behind each claim.
  • List findings and recommendations, explain a recommendation, show metric trends and freshness, and tell you which connected source each number came from.
  • Search and open individual Business Brain records (facts, products, competitors, insights) for the businesses you authorized.

It cannot

  • See a business you did not authorize, or one added after you approved.
  • See your Zylx password, or the credentials and tokens of Shopify, Google or any other provider you connected to Zylx. It only ever receives results.
  • Change anything on a read-only connection. A read-only connection causes zero writes to your business — ever.
  • Apply a change on its own. Where a connection may propose changes, each proposal lands in your Approval Queue in Zylx and is only carried out after you approve it there; ChatGPT additionally asks you to confirm every write action in the conversation.

Plan compatibility (ChatGPT)

Only what OpenAI documents. Yes means OpenAI states the plan can do it; Admin enables means a workspace admin or owner must turn it on; Unverified means OpenAI has not stated it either way and we will not guess. Claude, Claude Code and Codex availability is described above.

PlanDiscover pluginInstall pluginConnect custom app (developer mode)Read toolsWrite toolsFull MCPApps SDK UICompany knowledgeDeep ResearchAgent mode
FreesourceUnverifiedUnverifiedNoUnverifiedNoNoUnverifiedNoUnverifiedUnverified
GosourceUnverifiedUnverifiedNoUnverifiedNoNoUnverifiedNoUnverifiedUnverified
PlussourceUnverifiedUnverifiedYesYesUnverifiedUnverifiedUnverifiedNoUnverifiedUnverified
ProsourceUnverifiedUnverifiedYesYesNoNoUnverifiedNoUnverifiedUnverified
BusinesssourceUnverifiedAdmin enablesAdmin enablesAdmin enablesAdmin enablesAdmin enablesUnverifiedAdmin enablesUnverifiedUnverified
EnterprisesourceUnverifiedAdmin enablesAdmin enablesAdmin enablesAdmin enablesAdmin enablesUnverifiedAdmin enablesUnverifiedUnverified
EdusourceUnverifiedAdmin enablesAdmin enablesAdmin enablesAdmin enablesAdmin enablesUnverifiedAdmin enablesUnverifiedUnverified
  • Free: Not listed as eligible for Developer mode, so a custom Zylx app cannot be added. Directory access for the published plugin is not documented per plan.
  • Go: Not listed as eligible for Developer mode. Directory access for the published plugin is not documented per plan.
  • Plus: Listed as eligible for Developer mode on the web. Whether Plus gets write tools through a custom MCP app is not stated in the saved docs — unverified, never yes.
  • Pro: Developer mode on the web; custom MCP servers are read/fetch only, so Zylx write tools are not available to Pro through a custom app.
  • Business: Full MCP including writes is a web-only beta; only workspace admins/owners can enable Developer mode and publish workspace apps, and published apps use a frozen tool snapshot.
  • Enterprise: Same as Business: web-only beta, admin/owner enablement, frozen tool snapshot for published workspace apps.
  • Edu: Same as Business: web-only beta, admin/owner enablement, frozen tool snapshot for published workspace apps.

Sources: ChatGPT Developer mode, Developer mode and MCP apps in ChatGPT. Zylx ships no custom in-chat UI today, so the Apps SDK UI column describes the platform, not Zylx.

Zylx plan requirement for Business Brain access

Reading your Business Brain from an assistant is part of Zylx's paid plans (Pro and above). The requirement is per business, not per connection: a connection may be authorized for several businesses, and each one is checked against its own plan when a tool call reaches it. A business on the free plan — or on a paid plan whose subscription is no longer active — is not readable over MCP.

What a refused connection sees

  • The connection itself still works. Sign-in, the approval screen and the businesses you authorized are unaffected — only the Business Brain read is refused.
  • The assistant gets a plain refusal for that business, not an error and not partial data: “Business Brain access over MCP is not available on this business's current Zylx plan”, with a link back to this section.
  • If the connection is authorized for several businesses, the ones on an eligible plan answer normally and the ineligible one is reported by name as needing a plan — nothing is silently dropped.
  • No business data is returned by a refused call, and nothing about the refusal changes what the connection is authorized for.

How to check the plan on a business

  • Sign in to Zylx and open zylx.studio/billing for that business. It names the current plan and the subscription status Zylx is reading.
  • The plan is read from your billing record only, so it is the same answer Zylx gives your assistant.
  • A subscription that has lapsed (payment past due, or cancelled and past its period end) counts as free until it is active again.

This section describes access, not pricing. Nothing is sold inside your assistant, and Zylx never asks an assistant to buy or upgrade anything.

Something not working?

Email support@zylx.studio with the assistant you are using and what you saw. Our support page explains what to expect, and the privacy policy describes exactly what an assistant's provider receives when you connect it.

For developers

Zylx is one remote MCP server (streamable HTTP) for every assistant, protected by OAuth 2.1 with PKCE (S256). Clients discover the authorization server from the protected-resource metadata; ChatGPT registers through Client ID Metadata Documents when advertised and falls back to dynamic client registration. Tokens are bound to the explicit business set chosen at consent; a refresh can never widen it.

MCP endpoint
https://zylx.studio/api/mcp
Protected resource metadata
https://zylx.studio/.well-known/oauth-protected-resource
Authorization server metadata
https://zylx.studio/.well-known/oauth-authorization-server
OpenID configuration
https://zylx.studio/.well-known/openid-configuration

ChatGPT — exact steps

  1. Once Zylx Studio is listed (public path): open the ChatGPT Plugins directory at https://chatgpt.com/plugins, search for Zylx Studio, and choose Connect.
  2. Until then (private path): in ChatGPT, open Settings → Security and login → turn on Developer mode. Developer mode is web-only, and on Business, Enterprise and Edu a workspace admin or owner must enable it.
  3. Go to https://chatgpt.com/plugins, select the + button, name it Zylx Studio, and paste the MCP server URL: https://zylx.studio/api/mcp
  4. Choose OAuth. ChatGPT discovers Zylx sign-in from the server URL — there is no token to paste.
  5. Sign in to Zylx when the approval screen opens. All current businesses are pre-selected; uncheck any you do not want; businesses added later are never included automatically.
  6. Approve, then select Scan Tools (or Refresh) in ChatGPT so it reads the Zylx tool list.
  7. In a conversation, add Zylx Studio from the tools or Developer mode menu.
  8. Ask ChatGPT: "List my Zylx workspaces" or "Read my Zylx Business Brain".

Claude — exact steps

  1. On claude.ai or Claude Desktop: open Settings → Connectors → Add custom connector.
  2. Paste the Zylx MCP server URL: https://zylx.studio/api/mcp
  3. When Claude opens the Zylx sign-in, approve access — that's the whole connection (OAuth; no token to paste).
  4. Using Claude Code or another header-capable client instead? Generate a token above and use the ready-made config below — it passes the token as a Bearer Authorization header.
  5. Save and test.
  6. Ask Claude: "List my Zylx workspaces" or "Read my Zylx Business Brain".

Claude Code — exact steps

  1. In a terminal, run: claude mcp add --transport http --scope user zylx-studio https://zylx.studio/api/mcp
  2. Open Claude Code and run /mcp, then choose Zylx Studio → Authenticate.
  3. Sign in to Zylx in the browser, choose the businesses, and approve.
  4. Return to Claude Code and confirm the server shows Connected.
  5. Ask Claude Code: "List my Zylx workspaces" or "Read my Zylx Business Brain".

Codex — exact steps

  1. In Codex, add a remote MCP server named zylx-studio with the URL below (or run: codex mcp add zylx-studio --url https://zylx.studio/api/mcp).
  2. Start OAuth from the MCP settings or run: codex mcp login zylx-studio.
  3. Sign in to Zylx, choose the businesses, and approve.
  4. The same configuration is available to Codex desktop, CLI, and IDE.
  5. Ask Codex: "List my Zylx workspaces" or "Read my Zylx Business Brain".

Tool annotations (readOnlyHint / destructiveHint / openWorldHint) are advertised on every tool and match its real behaviour; assistants treat anything not read-only as a write and ask for confirmation.