Repository navigation
Releases
v0.3.2
v0.3.1
What's Changed
- Update uv-build requirement from <0.12.0,>=0.11.32 to >=0.12.0,<0.13.0 by @dependabot[bot] in #31
- Return counted envelopes from the five batch mail writes by @plecos in #32
- Cap mcp below 2.0, which deletes mcp.server.fastmcp by @plecos in #33
- Bump cryptography from 49.0.0 to 50.0.0 by @dependabot[bot] in #34
- Bump version to 0.3.1 by @plecos in #35
Full Changelog: v0.3.0...v0.3.1
v0.3.0
v0.2.0
What's Changed
- Assert whole Received values instead of a host substring by @plecos in #22
- Bump actions/download-artifact from 7 to 8 by @dependabot[bot] in #23
- Add forward_draft: forward email keeping formatting and attachments by @plecos in #24
- Make the send gate a bundle setting, and draft instead of refusing by @plecos in #25
- Report the running version, and whether a newer one exists by @plecos in #26
- Bump the version to 0.2.0 by @plecos in #27
Full Changelog: v0.1.0...v0.2.0
v0.1.0
First release. An MCP server that exposes a Zoho account — Mail, Calendar, Contacts, and Mail's Tasks, Notes, Bookmarks and Groups, plus Calendar's Resource Booking — as 40 tools to any MCP-compatible client.
It runs locally over stdio. No listening socket, no hosted endpoint, no third-party relay; the only outbound calls are to Zoho's own REST APIs.
Install
As a Claude Desktop extension — download zoho-mcp-0.1.0.mcpb below and install it from Settings → Extensions. One bundle covers Windows, macOS and Linux; there is nothing compiled in it, and this exact file was launched on all three platforms in CI before the release was cut.
Because the extension has required configuration, Claude Desktop installs it disabled — you have to switch it on yourself. Then run the authenticate tool once.
From a checkout — see the README.
Requirements
- uv on your PATH. Claude Desktop does not supply one. You do not need Python — uv downloads and manages its own.
- A Server-based Application registered in the Zoho API Console, for its client id and secret.
- On Linux, a Secret Service keyring backend (gnome-keyring, KWallet, or
keyrings.alt). The refresh token lives in the OS credential store; headless servers, WSL and containers often have no backend, and without one the server starts but cannot complete authentication.
Mail composition is draft-first
The one operation here that is irreversible and reaches another person is the one that's off by default.
create_draftandreply_draftalways work and always land in Drafts.send_emailrefuses — before making any network call — unless the operator setsZOHO_ALLOW_AUTO_SEND=truein the server's environment. It is deliberately not a checkbox in the extension's settings form.- There is no send-a-reply tool at any setting. Replies quote incoming mail, incoming mail is untrusted input, and a message in your mailbox can contain text aimed at talking an assistant into sending something.
See SECURITY.md for the full reasoning and what counts as a vulnerability here.
Correctness is the server's job, not the caller's
Every date and time comes back already converted to the mailbox's own local offset, fetched live rather than stored in config where it would go stale. Epoch strings become ISO 8601, HTML bodies become plain text, and RFC 2047 encoded subjects are decoded — each in exactly one place that every tool calls through. Bounds that Zoho accepts silently but truncates invisibly are enforced locally.
That rule exists because of a real failure: one session converted UTC correctly and a later session, same server and same data, displayed the raw UTC digits mislabelled as local time.
Built against the live API, not the docs
No feature here was considered done until it had run against a real Zoho account, and that turned out to matter. docs/zoho-api-notes.md is the residue: fields documented optional that are required, a mandatory field with a typo in its name, endpoints documented at URLs that 404, and field names that contradict their contents — sentDateInGMT is not GMT, previousFolderId is not a parent pointer, isPrev is not a paging direction.
That document is useful whatever you build on.
Known limitations
- Single user. One account, one OAuth token. No hosting, no multi-tenancy. If you need a team on a shared server, use Zoho's own MCP — docs/vs-zoho-mcp.md compares the two honestly, including where theirs is the better choice.
- Thread fields are not surfaced.
threadId/threadCountcould not be distinguished on any real data available, so they're documented as unknown rather than guessed at. - No attachment parsing.
get_attachmentreturns text when the content is text; a PDF or Word document comes back described but not decoded. - Resource free/busy appears unavailable through Zoho's API;
list_branches/list_resourceswork, per-resource availability does not. - Pre-1.0, single maintainer, no SLA.
Verification
691 tests. Lint, type-check and the full suite run on every push; the release bundle is unpacked and driven through an MCP handshake on Windows, Apple Silicon macOS and Linux before publication.
Full history: 21 merged pull requests · commits