Zoho Inventory + Muse
Connect Zoho Inventory to Muse
Prepare a grounded stock and order briefing
Read items with Muse and Agent200. Prepare a stock and order briefing using the connected user’s own Zoho Inventory account.
On this page
Overview
Use Muse to prepare a short stock and order briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.
Start with one identified item. Preserve returned item, stock, sales-order and purchase-order fields; report missing data and keep the workflow read-only.
Provider reference: Zoho Inventory API.
- Connector
- Zoho Inventory
- Works with
- Muse · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- 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 Inventory enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Zoho Inventory account. They approve access once, on Zoho Inventory'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 Inventory to Muse
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore 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
Step 2: Create the custom connector
Connect to
https://api.agent200.com/mcp/over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.Muse chatMCP: 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
Step 3: Inspect read tools
Confirm the Zoho Inventory operations and schemas advertised by the connection.
-
4
Step 4: Authorize Zoho Inventory
Connect the intended user and test one accessible item.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Zoho Inventory item I identify and prepare a stock and order briefing. Name the source and use only item, stock, sales-order and purchase-order fields. State access gaps; do not change records.
What should come back
- The selected item is identified.
- Only the returned item, stock, sales-order and purchase-order fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected item ID, account scope, read permission and pagination. Stock can vary by warehouse and timing. State the organization, location and returned quantity type; do not infer availability from an item name.
Get your API key
Create a key in the Agent200 dashboard. It reaches Zoho Inventory 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 Inventory to Muse.
Goal: connect Zoho Inventory to Muse with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-inventory/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 Inventory 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 Inventory request returns an authorization link if the user has not connected Zoho Inventory yet: show it to them and continue once they have approved access on Zoho Inventory's own page. 5. Check it works with this request: "Read the Zoho Inventory item I identify and prepare a stock and order briefing. Name the source and use only item, stock, sales-order and purchase-order fields. State access gaps; do not change records." What should come back: - The selected item is identified. - Only the returned item, stock, sales-order and purchase-order fields are reported. - Access gaps and missing context are explicit; 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 Inventory, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-inventory/framework/muse.md
Zoho Inventory tools Muse can call
-
List items
Readzoho_inventory_list_itemsFind items and returned stock fields in the selected organization.
-
Read an item
Readzoho_inventory_get_itemRetrieve one item by ID.
-
List sales orders
Readzoho_inventory_list_sales_ordersFind sales orders in scope.
-
Read a sales order
Readzoho_inventory_get_sales_orderRetrieve one sales order and its returned status.
-
List purchase orders
Readzoho_inventory_list_purchase_ordersFind purchase orders in scope.
No tool matches that search.
How it works
-
01
You ask Muse
In your own words, for something in Zoho Inventory.
-
02
Muse picks a tool
It sees the Zoho Inventory tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Zoho Inventory connection, within the tools and scopes your project allows.
-
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 Inventory account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Inventory enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected item ID, account scope, read permission and pagination. Stock can vary by warehouse and timing. State the organization, location and returned quantity type; do not infer availability from an item name.
FAQ
How do I verify this result?
Compare the named item and returned item, stock, sales-order and purchase-order fields with the source. Treat missing information as missing, not as a fact.
