This guide covers the end-to-end process for implementing Zoho MCP: from creating your first server and adding tools, through to connecting AI clients, managing authorisation, monitoring usage, and inviting team members.

Creating an MCP Server

Open the Zoho MCP Console and select "Create MCP Server". Provide a name for the server and confirm. The system generates the server instance and makes it available for tool configuration.

Alternatively, you can use a pre-configured server template such as "CRM Data and Metadata Operations", which comes ready with tools already set up for common workflows. Authorise the template and customise it as needed.

Adding Tools

Native Zoho Service Tools

Navigate to the Tools section within your server and select "Add Tools". Search or browse the list of available Zoho services, tick the boxes next to the tools you need, and confirm. The tools are added to your server immediately.

Third-Party Service Tools

The process for adding third-party tools follows the same pattern. Search the available integrations, select the tools you need, and confirm. Both native and third-party tools are managed through the same interface.

Connecting MCP Clients

Once tools are configured, copy the MCP URL from the Connect section of your server. This URL, which includes a secure API key, is what each client uses to communicate with the server. The following clients are supported:

• Claude.ai
• ChatGPT
• Cursor (supports both automatic and manual configuration)
• Windsurf
• VS Code (supports both automatic and manual configuration)
• Custom MCP clients (requires HTTP or Streamable Transport support)

Most clients are configured via an mcp_config.json file containing a standardised code snippet with the MCP URL inserted. Each client's own settings provide guidance on where this file should be placed or how to add the connector.

Managing Authorisation

Two authorisation models are available:

• Authorise on Demand. The default for Zoho services. Each user authenticates individually when they first use the server's tools.
• Authorise via Connections. Required for third-party services. A Super Admin shares OAuth tokens with the team, so individual users do not need to authenticate separately.

You can switch between authorisation types or revoke existing authorisations at any time from the Connections section.

Server Management

From the ellipsis menu on a server, administrators can temporarily disable or re-enable the server, or delete it permanently when it is no longer needed.

Logs and Monitoring

The Logs section provides an indexed record of all tool accesses. You can filter by timezone, status, tool type, ZUID, and execution ID to narrow results. Logs are retained for 30 days, after which they are automatically deleted.

Collaborators and Team Access

Use the Collaborators feature to give team members access to a shared MCP server. Invite people by email, assign Admin or User roles, edit permissions, and remove access as required. Only Super Admins can delete an organisation, and all collaborators must be removed before deletion can proceed.