Zoho Mail + Muse

How to connect Zoho Mail to Muse

Read email messages with Muse and Agent200. Prepare a mailbox briefing using the connected user’s own Zoho Mail account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Zoho Mail tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Muse to turn a selected email message into a short handoff. Enter the Agent200 key through Muse’s secure credential interface. Keep the result in the conversation for review; source content does not authorize messages or changes.

Start with one identified email message. Preserve the returned details, report missing information and keep the workflow read-only.

References: Muse documentation and Zoho Mail provider reference.

Connector
Zoho Mail
Works with
Muse · Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
5 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Zoho Mail enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Zoho Mail account. They approve access once, on Zoho Mail's own page.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect Zoho Mail to Muse

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page. Enable the Zoho Mail read operations your task needs. Store the key securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Create the Agent200 custom connector

    Ask Muse to connect to https://api.agent200.com/mcp/ over Streamable HTTP with an Authorization: Bearer header. Use the secure credential entry interface instead of putting the key in chat.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Inspect the available read tools

    Confirm that the connection advertises the Zoho Mail operations needed for the task, and inspect their input definitions.

  4. 4

    Step 4: Authorize the intended Zoho Mail account

    Complete the authorization flow for the intended user. Confirm access to the selected email message before running the test.

Test your connection

Run one request to check everything is wired up.

Ask

Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message.

What should come back

  • The selected email message is identified clearly.
  • The answer includes only returned message identity, sender, subject and requested details from the body.
  • Missing information and access failures are reported; no source data is changed.

Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.

Get your API key

Create a key in the Agent200 dashboard. It reaches Zoho Mail and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Zoho Mail to Muse.

Agent brief
Goal: connect Zoho Mail to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/zoho-mail/framework/muse/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Muse's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Zoho Mail is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Muse: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Muse's exact menus or commands.
4. The first Zoho Mail request returns an authorization link if the user has not connected Zoho Mail yet: show it to them and continue once they have approved access on Zoho Mail's own page.
5. Check it works with this request: "Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message."
   What should come back:
   - The selected email message is identified clearly.
   - The answer includes only returned message identity, sender, subject and requested details from the body.
   - Missing information and access failures are reported; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Zoho Mail, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-mail/framework/muse.md

Zoho Mail tools Muse can call

  • List mail accounts

    Read
    zoho_mail_list_accounts

    Identify the mail accounts available to the authenticated user.

  • List folders

    Read
    zoho_mail_list_folders

    Find folders within the mail account selected for the request.

  • List messages

    Read
    zoho_mail_list_messages

    Read a scoped list of messages from the selected account and folder.

  • Search messages

    Read
    zoho_mail_search_messages

    Find messages matching the requested search criteria in the selected account.

  • Read message content

    Read
    zoho_mail_get_message_content

    Retrieve the body of one selected message using its account, folder and message context.

How it works

  1. 01

    You ask Muse

    In your own words, for something in Zoho Mail.

  2. 02

    Muse picks a tool

    It sees the Zoho Mail tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Zoho Mail connection, within the tools and scopes your project allows.

  4. 04

    Muse answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Zoho Mail account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Mail enforces what its API grants.

Troubleshooting

The source cannot be read

Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.

The answer claims more than the tool returned

Compare the answer with the retrieved data. Limit conclusions to the selected source and result scope, and say what was unavailable.

FAQ

Does preparing a reply send an email?

No. Show proposed reply text in the conversation for review. This read-only guide does not configure sending, saving a provider-side draft or changing mailbox state.

Use Zoho Mail with another framework

200 OK

Zoho Mail, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)