Zoho Projects MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP server (optional, for remote access) | 3001 |
| ALLOWED_HOSTS | No | Allowed hosts for HTTP server (optional, for remote access) | 127.0.0.1,localhost |
| ZOHO_CLIENT_ID | Yes | Your Zoho OAuth client ID | |
| ZOHO_PORTAL_ID | Yes | Your Zoho Projects portal ID | |
| ALLOWED_ORIGINS | No | Allowed origins for HTTP server (optional, for remote access) | http://localhost:3000 |
| ZOHO_API_DOMAIN | No | The Zoho API domain for your region (e.g., https://projectsapi.zoho.com for US, https://projectsapi.zoho.in for India) | https://projectsapi.zoho.com |
| ZOHO_ACCESS_TOKEN | Yes | Your Zoho OAuth access token | |
| ZOHO_CLIENT_SECRET | Yes | Your Zoho OAuth client secret | |
| ZOHO_REFRESH_TOKEN | Yes | Your Zoho OAuth refresh token | |
| ZOHO_ACCOUNTS_DOMAIN | No | The Zoho accounts domain for your region (e.g., https://accounts.zoho.com for US, https://accounts.zoho.in for India) | https://accounts.zoho.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_portalsA | Retrieve all Zoho Projects portals |
| get_portalB | Get details of a specific portal |
| list_projectsB | List all projects in a portal |
| get_projectA | Get details of a specific project |
| create_projectC | Create a new project |
| update_projectB | Update an existing project |
| delete_projectA | Delete a project (moves to trash) |
| list_tasksB | List tasks from a project or portal |
| get_taskC | Get details of a specific task |
| create_taskC | Create a new task in a project |
| update_taskC | Update a task |
| delete_taskB | Delete a task |
| list_issuesB | List issues from a project or portal |
| get_issueB | Get details of a specific issue |
| create_issueD | Create a new issue |
| update_issueD | Update an issue |
| list_phasesB | List phases/milestones from a project |
| create_phaseC | Create a new phase/milestone |
| searchC | Search across portal or project |
| list_usersA | List users in a portal or project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource (issue, phase, project, task, portal, user) and action (create, get, list, update, delete, search), making it easy for an agent to select the right one. Overlap is minimal, such as list_issues vs. search, but their descriptions clarify distinct use cases.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_issue, get_project, list_tasks, update_task, and delete_project. There are no deviations in naming conventions, making the set predictable and easy to navigate for an agent.
With 20 tools, the count is slightly high but reasonable for a project management domain covering multiple resources like issues, tasks, projects, portals, phases, and users. It feels comprehensive rather than bloated, though it borders on the upper limit of ideal scope.
The tool surface provides complete CRUD/lifecycle coverage for the domain, including create, get, list, update, and delete operations for key resources like issues, tasks, and projects. There are no obvious gaps, and tools like search and list_users add useful functionality, ensuring agents can handle typical workflows without dead ends.