Skip to main content
skill CX Codex

catalyst-zoho-mcp — Claude Code skill: Zoho Catalyst infrastructure

This skill wires an AI agent to the Zoho Catalyst MCP server so tables, buckets and cache get created from plain chat instead of the console.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add catalystbyzoho/agent-skills --skill catalyst-zoho-mcp -a claude-code
Open on GitHub

What catalyst-zoho-mcp does

The skill teaches an agent to drive Zoho Catalyst through CatalystbyZoho_* tools. DataStore tables, Stratus buckets, cache — all of it runs from the chat, and the agent reports which tool it called and what came back. No console tab required.

Here is the flow. First the skill checks whether CatalystbyZoho_* tools show up in the tool list. If they don't, it hard-stops and writes no code until the MCP server is connected. Then comes the pre-flight sequence: confirm the data center, then call CatalystbyZoho_List_All_Organizations and CatalystbyZoho_List_All_Projects to set project context. The data center is where people trip — pick the wrong one and the org list comes back empty. /catalyst-by-zoho:switch-dc switches it.

Two setup paths exist. The global MCP server means adding your DC-specific URL to the client config and authorizing once in a browser. The personal server means building your own at mcp.zoho.com, picking tools and getting a URL with a token baked in. You need an MCP-capable host: Claude Desktop, VS Code with GitHub Copilot, or Cursor.

What it helps with

  • create a DataStore table and columns without opening the Catalyst console
  • list organizations and projects before touching infrastructure
  • switch data centers when the org list returns empty
  • debug why the MCP tools refuse to connect
  • run a data query against Catalyst from inside the agent chat

Example prompts for the agent

  • list my Catalyst organizations through MCP
  • create a DataStore table with name and email columns
  • switch the data center to EU with /catalyst-by-zoho:switch-dc

How to install catalyst-zoho-mcp

1Skills CLI (Vercel)

npx skills add catalystbyzoho/agent-skills --skill catalyst-zoho-mcp -a claude-code

2Manually: put the files in place

~/.claude/skills/catalyst-zoho-mcp/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/catalyst-zoho-mcp/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about catalyst-zoho-mcp

How do I install catalyst-zoho-mcp in Claude?

Run npx skills add catalystbyzoho/agent-skills --skill catalyst-zoho-mcp -a claude-code. The skill lands at ~/.claude/skills/catalyst-zoho-mcp/SKILL.md.

What does catalyst-zoho-mcp do?

It gives an agent access to Zoho Catalyst infrastructure through CatalystbyZoho_* MCP tools: tables, buckets, cache. You describe what you want in plain language.

What do I need before the skill works?

An MCP-capable host — Claude Desktop, VS Code with GitHub Copilot, or Cursor — plus a connected Catalyst MCP server. Without visible CatalystbyZoho_* tools the skill stops and writes no code.

Source text

SKILL.md · Apache-2.0
---
name: catalyst-zoho-mcp
description: "Catalyst Zoho MCP — manage Catalyst infrastructure (tables, buckets, cache) via CatalystbyZoho_* MCP tools using natural language. Trigger on 'Zoho MCP', 'MCP tools', 'catalyst MCP', 'CatalystbyZoho', 'create table with AI', 'MCP setup', 'MCP config', 'global MCP server', 'infrastructure as conversation', 'MCP first', 'avoid Catalyst console', or 'use MCP instead of console'."
compatibility: "Requires an MCP-capable AI host: Claude Desktop, VS Code with GitHub Copilot, or Cursor."
metadata:
  version: "2.2.3"
---

## How It Works

1. **Check if MCP is connected** — Look for `CatalystbyZoho_*` tools in your tool list.

2. **MCP NOT connected — HARD STOP.**
   Do NOT write any code, create any files, or call any SDK.
   Ask the user which setup path they prefer, then load `references/zoho-mcp.md` and follow only that path.
   Do not proceed to step 3 until the user confirms `CatalystbyZoho_*` tools are visible in their client.

   > **To work with Catalyst via MCP, choose your setup path:**
   >
   > **Option A — Global MCP Server** *(recommended)*
  > Add your DC-specific URL to your AI client config, authorize once via browser, done. No console needed.
  > US: `https://catalyst.zohomcp.com/mcp/message`, EU: `https://catalyst.zohomcp.eu/mcp/message`, IN: `https://catalyst.zohomcp.in/mcp/message`, AU: `https://catalyst.zohomcp.com.au/mcp/message`, CA: `https://catalyst.zohomcp.ca/mcp/message`, SA: `https://catalyst.zohomcp.sa/mcp/message`, JP: `https://catalyst.zohomcp.jp/mcp/message`, UAE: `https://catalyst.zohomcp.ae/mcp/message`.
   >
   > **Option B — Personal MCP Server** *(custom/team setup)*
   > Create your own server at mcp.zoho.com, select tools, get a personal URL with a token embedded.
   >
   > *Which would you prefer?*

3. **Pre-flight sequence** — In order:
   - **Confirm DC first.** Wrong DC = empty org list. Use `/catalyst-by-zoho:switch-dc` to switch data centers if `CatalystbyZoho_List_All_Organizations` returns empty or the wrong org.
   - Run `CatalystbyZoho_List_All_Organizations` → `CatalystbyZoho_List_All_Projects` to set project context before any other MCP tool call.
4. **Load `references/zoho-mcp.md`** — for the full tool catalog, execution flow, and common error fixes.
5. **If the query involves DataStore** (create table, add columns, query data) — also load `references/mcp-datastore.md`.
6. **Answer** — Call the appropriate `CatalystbyZoho_*` tool directly. Show the user what tool was called and what it returned.

## Triggers

Use this skill for: "Zoho MCP", "MCP tools", "catalyst MCP", "create table with AI", "MCP DataStore", "MCP Cache", "MCP Stratus", `zoho-mcp-server`, "MCP setup", "MCP config", "global MCP server", "infrastructure as conversation", "Claude MCP Catalyst", "MCP tool error", "MCP not connecting", "use AI to create database table", or `CatalystbyZoho_` tool.

## References

| Reference | Load when the query is about… |
|-----------|-------------------------------|
| `references/zoho-mcp.md` | Global MCP server setup (all 3 clients), all available CatalystbyZoho_* tools, execution flow, org→project pre-flight sequence, common MCP errors |
| `references/mcp-datastore.md` | Creating tables/columns via MCP, DataStore column types, batch column creation, data type constraints |

© catalystbyzoho · Apache-2.0 · catalystbyzoho/agent-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set14

catalyst-functions Guides development and deployment for all 7 Zoho Catalyst serverless function types. Helps configure API Gateway routing, resolve CORS bugs, and handle file uploads. CX Codex +1 1,000installs catalyst-appsail Guides the agent through deploying a persistent server on Catalyst AppSail, whether a managed Node.js, Java or Python runtime or your own Docker container. CX Codex +1 1,000installs catalyst-by-zoho Guides Claude Code through building full-stack serverless apps on Catalyst by Zoho. Helps wire Functions, Slate, and storage via Zoho MCP tools and the CLI. CX Codex +1 1,000installs catalyst-authentication Guides user login, social auth, and OAuth connections in Zoho Catalyst. Prevents broken production deployments caused by mismatched ZAID identifiers. CX Codex +1 999installs catalyst-slate Walks your agent through deploying a frontend to Catalyst Slate: scaffold the app, configure slate-config.toml, ship the build. Handy when React or Next.js needs to live on Catalyst. CX Codex +1 1,000installs catalyst-cache A skill that teaches the agent to use Catalyst Cache: store temporary values in segments, read them back, and respect the TTL. Handy for session data. CX Codex +1 997installs catalyst-stratus A skill for Catalyst Stratus object storage: file uploads, signed URLs, multipart upload. Useful when your project keeps files in Stratus. CX Codex +1 994installs catalyst-nosql A skill that tells the agent how to work with Catalyst NoSQL tables: build items with NoSQLItem, insert, fetch and update records. CX Codex +1 991installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor