Zoho CRM + Hermes Agent
How to connect Zoho CRM to Hermes Agent
Read CRM records with Hermes Agent and Agent200. Prepare a sales briefing using the connected user’s own Zoho CRM account.
On this page
Overview
Inspect the Agent200 tools exposed in Hermes after configuration. Use the advertised schemas and names for the CRM record read; server prefixes and argument mappings should come from discovery, not from guessed catalogue names.
Start with one identified CRM record. Preserve the returned details, report missing information and keep the workflow read-only.
References: Hermes Agent documentation and Zoho CRM provider reference.
- Connector
- Zoho CRM
- Works with
- Hermes Agent · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 4 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 CRM enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Zoho CRM account. They approve access once, on Zoho CRM's own page.
- Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.
Connect Zoho CRM to Hermes Agent
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers Zoho CRM and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Store your key in ~/.hermes/.env
Keep the key out of
config.yaml: Hermes reads it from~/.hermes/.env.~/.hermes/.envMCP: Hermes Agent key in ~/.hermes/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Add the server to ~/.hermes/config.yaml
Add an entry under
mcp_serverswith the URL and the Authorization header. Do not settransport: sse: Agent200 serves streamable HTTP.~/.hermes/config.yamlMCP: Hermes Agent config.yaml entry mcp_servers: agent200: url: "https://api.agent200.com/mcp/" headers: Authorization: "Bearer ${AGENT200_API_KEY}" -
4
Step 4: Reload and test
In a running session, run
/reload-mcp, or restart Hermes. Then check what the server returned from a terminal.TerminalMCP: Hermes Agent reload and test # In a running Hermes session: /reload-mcp hermes mcp test agent200 hermes mcp list -
5
Step 5: Connect your Zoho CRM account
The first time you ask Hermes Agent for something in Zoho CRM, Agent200 returns an authorization link. Open it and approve access on Zoho CRM's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Zoho CRM deal I identify in the specified module and prepare a sales handoff from the returned fields. Include its owner, stage and relevant dates when available. Ask me to resolve missing or ambiguous identifiers. Do not change the record.
What should come back
- The selected CRM record is identified clearly.
- The answer includes only returned record identity, owner, stage and relevant dates.
- Missing information and access failures are reported; no source data is changed.
Confirm the selected organization, module and record ID. Check the fields and scopes available to the connected user. Distinguish a failed read from an empty record.
Get your API key
Create a key in the Agent200 dashboard. It reaches Zoho CRM and every other connector enabled for your project.
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 CRM to Hermes Agent.
Goal: connect Zoho CRM to Hermes Agent with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-crm/framework/hermes-agent/ 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 Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Zoho CRM is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Hermes Agent: 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 Hermes Agent's exact menus or commands. 4. The first Zoho CRM request returns an authorization link if the user has not connected Zoho CRM yet: show it to them and continue once they have approved access on Zoho CRM's own page. 5. Check it works with this request: "Read the Zoho CRM deal I identify in the specified module and prepare a sales handoff from the returned fields. Include its owner, stage and relevant dates when available. Ask me to resolve missing or ambiguous identifiers. Do not change the record." What should come back: - The selected CRM record is identified clearly. - The answer includes only returned record identity, owner, stage and relevant dates. - 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 CRM, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-crm/framework/hermes-agent.md
Zoho CRM tools Hermes Agent can call
-
Search records
Readzoho_crm_search_recordsFind matching records within the CRM module selected for the request.
-
Read a record
Readzoho_crm_get_recordRead one identified contact, account, lead or deal from its module.
-
List records
Readzoho_crm_list_recordsRetrieve records from a selected module with an explicit field and result scope.
-
Read related records
Readzoho_crm_get_related_recordsRead an available related list for a selected CRM record, such as associated notes.
No tool matches that search.
How it works
-
01
You ask Hermes Agent
In your own words, for something in Zoho CRM.
-
02
Hermes Agent picks a tool
It sees the Zoho CRM tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Zoho CRM connection, within the tools and scopes your project allows.
-
04
Hermes Agent 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 CRM account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho CRM enforces what its API grants.
Troubleshooting
The source cannot be read
Confirm the selected organization, module and record ID. Check the fields and scopes available to the connected user. Distinguish a failed read from an empty record.
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
How do I keep a deal briefing grounded?
Name the selected record and preserve the returned stage, owner and date meanings. Label absent information and separate next-step suggestions from CRM facts.
Which tool name should Hermes call?
Use the name and input schema advertised by the live MCP connection. The site’s catalogue identifiers describe operations, but server-prefixed names and actual arguments come from discovery.

