Docs Zorem AI Agent Connector Connecting Claude, ChatGPT and Codex

Connecting Claude, ChatGPT and Codex

Your agent has its own MCP address on your site. You add that address to your AI app, then either approve a sign-in or give the app the agent’s token. The connection acts as your agent only: it sees and does exactly what the agent is allowed.

AI Agent Connector → Agent → Connection

Copy the Agent’s Address

Under This agent’s address, click Copy. The address looks like https://your-site.com/wp-json/ai-agent-os/v1/mcp/agent/…. If it ever leaks, New address replaces it — every app connected to the old one stops working and has to be added again.

Signing in from Claude or ChatGPT needs your site to be served over HTTPS. On a site without it, the Connection section says so — connect with the agent’s token instead.
If the Connection section says This web server removes the Authorization header, no app can use the address yet: the sign-in appears to succeed, then every call is refused. It shows the line to add to your server configuration — see Troubleshooting & FAQ.

Claude (claude.ai and the Desktop App)

  • Click your name (bottom left) → Settings.
  • Open Connectors, then click Add custom connector.
  • Give it a name (for example Admin Assistant) and paste the agent’s address into the remote MCP server URL box. Leave the OAuth client ID and secret empty.
  • Click Add, then Connect on the connector that appears.
  • Sign in to your site as an administrator if asked, check that the screen names your agent and lists the tools it would get, then click Approve and connect.

The connector turns on and the agent’s tools appear in your chats.

ChatGPT

Developer mode has to be on first.

  • Click your name (bottom left) → Settings → Plugins.
  • Open Developer mode at the bottom of that list and switch it on.
  • Go back and click Browse plugins, then the + button beside the search box.
  • In New Plugin, type a name, leave Connection on Server URL and paste the agent’s address underneath.
  • Leave Authentication on OAuth, tick I understand and want to continue, then click Create.
  • Sign in to your site as an administrator, check that the screen names your agent, then click Approve and connect.

Pick it from the + menu inside a chat to use it.

The Approval Screen

When an app signs in, your site shows a Connection request screen before anything is handed over. It shows who is asking (the app’s own name for itself, and the address that publishes it), the agent it would connect as and every tool that agent holds, with destructive ones marked. Approving creates nothing and changes no permission: the app simply acts as your agent. Click Deny if you did not just start the connection yourself.

Codex (with a Token)

  • Issue a token in the Token card (see below) and copy it.
  • Put it in an environment variable named ZOREM_ADMIN_ASSISTANT_TOKEN.
  • Add the agent in a terminal with the command shown on the Connection section, which includes your agent’s address.
codex mcp add admin-assistant --url https://your-site.com/wp-json/ai-agent-os/v1/mcp/agent/… --bearer-token-env-var ZOREM_ADMIN_ASSISTANT_TOKEN

Other Apps (Cursor, VS Code, Claude Code)

Add a remote MCP server and paste the same address. An app that identifies itself with a client metadata document signs in the same way; one that cannot sign in connects with the agent’s token instead, sent as Authorization: Bearer <token>.

The Agent’s Token

OptionDescription
Apps that connect by signing in don’t need a token. Their sign-in keeps working when you issue a new token, and the Connection section names the app that was last approved.

Disconnecting an App

Remove the connector in the app, or revoke the agent on its Connection section (see Access, Safety & Customer Data).