Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

catalyst-zoho-mcp

Sterne0

Forks0

Aktualisiert25. Juni 2026 um 11:37

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', 'switch DC', 'change data center', or 'infrastructure as conversation'.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

catalystbyzoho

catalystbyzoho/claude-plugin

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

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', 'switch DC', 'change data center', or 'infrastructure as conversation'.
compatibility	Requires an MCP-capable AI host: Claude Code, Claude Desktop, VS Code with GitHub Copilot, or Cursor.
metadata	{"version":"2.2.0"}

How It Works

Check if MCP is connected — Look for CatalystbyZoho_* tools in your tool list.
⛔ 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?
DC switch request? — If the user asks to switch data centers (e.g. "connect to IN DC", "switch to EU", "logout of MCP server"), load references/dc-switching.md and follow it. Do not use zoho-mcp.md for this.
Pre-flight sequence — Always run CatalystbyZoho_List_All_Organizations → CatalystbyZoho_List_All_Projects first to set project context before any other MCP tool call.
Load references/zoho-mcp.md — for the full tool catalog, execution flow, and common error fixes.
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", CatalystbyZoho_ tool, "switch DC", "change data center", "connect to IN DC", "switch to EU", "logout of MCP server".

References

Reference	Load when the query is about…
`references/zoho-mcp.md`	General MCP setup (Claude Desktop, Cursor, VS Code), all available CatalystbyZoho_* tools, execution flow, org→project pre-flight sequence, common MCP errors
`references/dc-switching.md`	Switching data centers on any client, including Claude Code plugin cache paths

Mehr aus diesem Repository

gleiches Repository

catalyst-appsail

catalystbyzoho/claude-plugin

Catalyst AppSail — persistent backend PaaS with managed runtimes (Node.js, Java, Python) and custom Docker containers. Trigger on 'AppSail', 'persistent server', 'Docker on Catalyst', 'X_ZOHO_CATALYST_LISTEN_PORT', or 'long-running process on Catalyst'. Do NOT use for stateless request/response handlers, event-driven functions, or scheduled jobs — use catalyst-functions instead.

2026-06-220

catalyst-authentication

catalystbyzoho/claude-plugin

Catalyst Authentication — user login/signup, ZAID, Web SDK auth flows, and OAuth token management via Connections. Trigger on 'authentication', 'login', 'signup', 'getCurrentUser', 'ZAID', 'isUserAuthenticated', 'signOut', 'Connections', or 'getAccessToken'. You MUST load this skill whenever implementing user login or protecting data — ZAID differs between Development and Production and is the #1 cause of auth failures after environment promotion. For Security Rules (function invocation control), route to catalyst-functions.

2026-06-220

catalyst-basics

catalystbyzoho/claude-plugin

Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.

2026-06-220

catalyst-datastore

catalystbyzoho/claude-plugin

Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', or 'ROWID'. You MUST load this skill whenever writing code that reads or writes Data Store data — ZCQL result wrapping and App User permissions are non-obvious and cause silent bugs if skipped.

2026-06-220

catalyst-functions

catalystbyzoho/claude-plugin

Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Trigger on 'write a function', 'catalyst function', 'API Gateway', 'Security Rules', 'function not found', 'function returns 401', 'busboy', 'middleware', 'function URL', 'environment variable in function', or any function type question. Do NOT use for persistent servers, long-running processes, WebSockets, or Docker deployments — use catalyst-appsail instead.

2026-06-220

catalyst-pricing

catalystbyzoho/claude-plugin

Catalyst pricing — free tier limits, pay-as-you-go rates, GB-seconds calculation, and cost estimation for functions, storage, and other services. Trigger on 'pricing', 'cost', 'free tier', 'how much does Catalyst cost', 'GB-seconds', 'billing', or 'will this be free'.

2026-06-220

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', 'switch DC', 'change data center', or 'infrastructure as conversation'.
compatibility	Requires an MCP-capable AI host: Claude Code, Claude Desktop, VS Code with GitHub Copilot, or Cursor.
metadata	{"version":"2.2.0"}

How It Works

Check if MCP is connected — Look for CatalystbyZoho_* tools in your tool list.
⛔ 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?
DC switch request? — If the user asks to switch data centers (e.g. "connect to IN DC", "switch to EU", "logout of MCP server"), load references/dc-switching.md and follow it. Do not use zoho-mcp.md for this.
Pre-flight sequence — Always run CatalystbyZoho_List_All_Organizations → CatalystbyZoho_List_All_Projects first to set project context before any other MCP tool call.
Load references/zoho-mcp.md — for the full tool catalog, execution flow, and common error fixes.
Answer — Call the appropriate CatalystbyZoho_* tool directly. Show the user what tool was called and what it returned.

Triggers

References

Reference	Load when the query is about…
`references/zoho-mcp.md`	General MCP setup (Claude Desktop, Cursor, VS Code), all available CatalystbyZoho_* tools, execution flow, org→project pre-flight sequence, common MCP errors
`references/dc-switching.md`	Switching data centers on any client, including Claude Code plugin cache paths