ChatGPT can use a Zoho MCP server as a connector, so you can ask it questions about your Zoho data and, if you allow it, have it take actions. Zoho lists ChatGPT among its supported MCP clients. This short guide covers what you need, the shape of the setup, how it differs from Claude, and what to check before connecting. For creating the server and adding tools, follow Zoho MCP Implementation Guide.
Menus move. OpenAI has renamed and relocated the settings for connectors and developer mode several times, so we describe what to look for rather than an exact click path. If a screen does not match, search ChatGPT's settings for Apps, Connectors, or Developer mode.
What you need
- A paid ChatGPT plan that allows custom connectors. Zoho's own guidance names Plus, Pro, and Team. OpenAI's plan rules change, and other business plans may also qualify, so check yours. The free plan is not suitable.
- Developer mode, where OpenAI requires it. Custom connectors have needed this to be switched on, and OpenAI labels it an elevated-risk setting because it lets the model take write actions through connected tools.
- An administrator's approval on workspace plans. On a business or enterprise workspace, an administrator may have to allow custom connectors first.
- A Zoho MCP server and its URL. ChatGPT connects only to remote servers over HTTPS, which Zoho MCP provides.
The setup in outline
- In the Zoho MCP console for your data centre, create a server and add only the tools you need. UK and Irish customers on the EU data centre use the EU console, not the .com one.
- Copy the server's MCP URL from its Connect section.
- In ChatGPT, turn on developer mode if it asks for it, then add a new custom app or connector. Give it a clear name and description, and paste the MCP URL into the MCP Server URL field.
- Start a new chat and switch the connector on for that conversation from the tools menu. Connectors are not always on by default.
- Try a harmless read-only request first, such as listing a few records.
Zoho's published steps only ask you to paste the URL. If ChatGPT also asks you to choose an authentication method and you are unsure which, stop and ask us rather than guessing.
How it differs from connecting Claude
| Point |
ChatGPT |
Claude |
| Extra switch needed | Developer mode, which carries an elevated-risk warning | None beyond a plan that allows custom connectors |
| Who can add it | You, or an administrator on workspace plans | You, or an administrator, depending on plan. Zoho notes that an organisation administrator is needed on some plans. |
| Using it in a chat | Usually enabled per conversation | Managed through connector settings |
| Stability of menus | Has changed repeatedly | Steadier, but also changes |
Before you connect: safety checks
- Treat the MCP URL as a password. Zoho says the URL contains a secure API key. Do not paste it into shared documents, chats, or emails.
- Start read-only. Expose only reading tools at first, and add write tools one job at a time. Our safe setup checklist applies to any assistant, not only Claude.
- Review each action before approving it. With developer mode on, ChatGPT can propose changes to your Zoho data. Read what it intends to do, not only what it says it did.
- Know where the data goes. What ChatGPT reads from Zoho goes to OpenAI. Check the terms of your ChatGPT plan, and see our data residency article if processing location matters.
When ChatGPT is a good choice
Our default for an outside assistant is Claude, for reasons set out in Using AI with Zoho. ChatGPT is a sensible choice when a business has already standardised on it, with contract terms and approvals in place, because a tool people are allowed to use beats a theoretically better one nobody can.
If it does not work
- No option to add a custom connector. Check that your plan supports it, that developer mode is on, and, on a workspace, that an administrator has allowed it.
- Connected, but no Zoho tools appear. Switch the connector on for the conversation, then check the tools you added in the Zoho MCP console.
- It stopped working after a change in Zoho. If you generated a new URL for the server, update it in ChatGPT.