# Zoho Bigin MCP connector The Zoho Bigin connector brings your Zoho Bigin users, roles, profiles and organization details into Claude, ChatGPT, Cursor and any MCP client, so your team can review who has access and tidy up seats by asking in plain language. Source: https://elaichi.ai/connectors/zohobigin/ ## Facts | | | | --- | --- | | Application | Zoho Bigin | | Category | CRM | | AI tools | 7 | | Authentication | Connects over OAuth | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Zoho Bigin is connected - List everyone in Zoho Bigin with the Administrator profile. - Which Zoho Bigin roles have no users assigned right now? - Show new Zoho Bigin users added in the last month. ## Connect Zoho Bigin in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Zoho Bigin. 2. Optionally set Share with, then press Connect. 3. Approve it in Zoho Bigin. Zoho Bigin's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Zoho Bigin tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Zoho Bigin to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Zoho Bigin to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Zoho Bigin to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Zoho Bigin to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Zoho Bigin tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Zoho Bigin through Elaichi ### See who has a seat in Zoho Bigin Sales operations. Pull the full list of Zoho Bigin users, spot accounts that belong to people who have moved teams, and know exactly who is working in the CRM today. ### Remove a departed rep's Zoho Bigin user IT. When someone leaves, look up their Zoho Bigin user and remove it from the same place you handle the rest of offboarding. ### Check which role a rep holds Revenue operations. List the roles set up in Zoho Bigin and confirm that each rep, manager and admin sits where they should before the next pipeline review. ### Count Zoho Bigin seats before renewal Finance. Get a current head count of Zoho Bigin users so the renewal quote matches the people who actually use the CRM. ### Review what each profile allows Sales leadership. Read through the profiles in Zoho Bigin to see which permission sets exist and who is on a broader profile than their job needs. ### Confirm your Zoho Bigin organization details Office administration. Pull up the current organization record and your own signed-in user to confirm the account, time zone and contact details are correct. ## Frequently asked questions ### How do I connect Zoho Bigin to Claude? Connect Zoho Bigin in Elaichi first: pick it from the list and sign in to your Zoho account with the usual Zoho login screen, then approve access. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and Zoho Bigin is ready. ### Does Zoho Bigin work with ChatGPT and Cursor as well as Claude? Yes. Once Zoho Bigin is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Zoho Bigin once and every client sees it. ### What can an AI agent actually do with my Zoho Bigin data? With this connector an agent can list the users in your Zoho Bigin account, look up a single user, and remove a user who should no longer have access. It can also read your organization details, confirm which Zoho Bigin user you are signed in as, and list the roles and profiles that control what people can see and do. It is built for managing who is in Zoho Bigin rather than editing deals or contacts. ### Does connecting Zoho Bigin give the AI everything in my account? No. Every request to Zoho Bigin runs as the person who signed in, so an agent can only see the users, roles and profiles that person's own Zoho Bigin permissions allow. Elaichi can narrow that further, for example by hiding the ability to remove users, but it can never grant more than the person already has in Zoho Bigin. ### Can my team share one Zoho Bigin connection? Yes. One admin connects Zoho Bigin in Elaichi and shares the connection with a team, and nobody else has to handle a Zoho password or credential. Each teammate still signs in to Elaichi as themselves, so the audit log records who looked up or removed a Zoho Bigin user, not just that the shared connection was used. ### Can I stop an agent from deleting or changing things in Zoho Bigin? Yes. Restrictions in Elaichi work per action, so you can allow listing Zoho Bigin users, roles and profiles while blocking the ability to remove a user. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, accidental or otherwise, can reach it. ### What happens to a Zoho Bigin connection when someone leaves? Offboarding that person in Elaichi ends their access to Zoho Bigin through every client at once. If they connected Zoho Bigin and shared it, the shared connection keeps working for everyone else on the team. When you want it gone completely, disconnecting Zoho Bigin once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ## All 7 Zoho Bigin tools Every tool below is callable through https://api.elaichi.ai/mcp once Zoho Bigin is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Zoho Bigin users** (List). A user is someone who has access to an organization in Bigin. Use this endpoint to get all users in the Zoho Bigin account. - **Get single Zoho Bigin user by ID** (Get). Use this endpoint to get a single user in the Zoho Bigin account. It always requires the ID to fetch. - **Delete a Zoho Bigin user by ID** (Delete). Use this endpoint to delete a single user in the Zoho Bigin account. It always requires the ID to delete a user. - **List all Zoho Bigin current organization** (List). An organization in Bigin represents a company. Use this endpoint to get the current company information in the Zoho Bigin account. - **List all Zoho Bigin me** (List). Use this endpoint to get the information about the currently authenticated user in the Zoho Bigin account. - **List all Zoho Bigin roles** (List). In Zoho Bigin, each organization has a defined set of roles that determine data access based on a hierarchy. These roles are assigned to users according to their responsibilities. Use this endpoint to retrieve a list of all the roles available in your organization. - **List all Zoho Bigin profiles** (List). In Bigin, profiles determine user permissions and control the actions users can perform within the application. Each user in the Bigin setup is assigned a profile that defines their level of access to organizational data. Use this endpoint to retrieve a list of all the profiles available in your organization.