integration-zoom

Configure Zoom Server-to-Server OAuth credentials on a remote Hermes VPS over SSH.

13|1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/paarths-collab/hstack --skill integration-zoom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-zoom
Source: https://github.com/paarths-collab/hstack/tree/main/skills/integration-zoom
Command: npx skills add https://github.com/paarths-collab/hstack --skill integration-zoom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill connects a self-hosted Hermes Agent to Zoom so an AI coding agent can manage Zoom meetings, users, webinars, and reports without manual API wiring. It is designed for SSH-first deployment on a VPS and makes the setup idempotent, rollback-safe, and easy to verify.

Core Features & Use Cases

  • Server-to-Server OAuth Wiring: Stores the three Zoom S2S credentials on the remote Hermes host and validates that token minting works.
  • Zoom API Operations: Supports common headless Zoom tasks such as listing meetings, creating meetings, and reading usage reports.
  • Safety and Guardrails: Explicitly refuses the hosted Zoom MCP path, warns when cloud recordings are requested, and checks activation, scopes, and token health before continuing.
  • Use Case: A developer wants their AI agent to manage Zoom scheduling from a VPS, so they run this Skill to configure credentials, reload the gateway, and confirm the API is reachable.

Quick Start

Ask the agent to connect Zoom to your remote Hermes VPS using Server-to-Server OAuth and provide the VPS details plus the Zoom app credentials.

Frequently Asked Questions about integration-zoom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Zoom to a self-hosted Hermes Agent on a VPS?

You connect Zoom to a self-hosted Hermes Agent on a VPS by configuring Server-to-Server OAuth credentials over SSH, validating live token minting, and reloading the gateway to enable headless automation for meetings and reports.

What is the best way to automate Zoom API operations on a remote VPS?

The best way to automate Zoom API operations on a remote VPS is using Server-to-Server OAuth wiring, which stores credentials idempotently and checks token health, activation, and scopes before executing headless tasks like creating meetings.

Why does my Zoom integration refuse the hosted MCP path?

Your Zoom integration refuses the hosted MCP path because the Skill explicitly avoids it for safety, choosing instead to validate live token minting directly on a remote Hermes host to ensure rollback-safe credential management.

Do I need Server-to-Server OAuth credentials to manage Zoom meetings from a VPS?

Yes, you need Server-to-Server OAuth credentials to manage Zoom meetings from a VPS, because the integration requires storing these three credentials on the remote host and validating live token minting before any headless API operations.

What are the limitations of using Zoom Server-to-Server OAuth for headless automation?

Limitations of using Zoom Server-to-Server OAuth for headless automation include explicit warnings when cloud recordings are requested, strict scope checks, and the necessity of idempotent credential storage and gateway reloads to maintain token health.

Can I use SSH to configure Zoom credentials on a remote Hermes host?

Yes, you can use SSH to configure Zoom credentials on a remote Hermes host, applying idempotent credential storage, validating token minting, and performing rollback-safe verification to ensure headless Zoom API operations are reachable.