Two Paths
The same question, answered two ways. On the left, a traditional integration — it handles the requests someone shipped. On the right, Claude with the MCP tools — it reads the schemas and works out what to do. Ask something nobody planned for and watch what happens.
Brain:
Hard-coded integration
Fixed handlers. Written by a developer, in advance.
Ask a question.
Claude + MCP
Reads the tool schemas. Chooses. Chains. Nobody wrote this.
Ask a question.
MCP Server
Seven MCP servers mirroring mcp.zoom.us. Claude connects here; every tool
call is a live call to your Zoom account.
No Zoom app connected. Click Setup to add and authorize your Zoom app.
Endpoints
The seven MCP servers Claude can connect to.
Tools
Every capability, listed once.
Meetings
Team Chat
Docs
Whiteboard
Tasks
Revenue Accelerator
MCP Client
Call Zoom's real hosted MCP servers at mcp.zoom.us, and diff their live tool
surface against ours.
tools/list against production Zoom
Pick a server and run.
Call a tool
This hits production Zoom.
JSON-RPC frames
No frames yet.
Does our mirror match production?
Run the diff.
Claude Connect
Point Claude at this platform.
No public HTTPS URL yet — claude.ai needs one. Set it below.
Public URL
The cloudflared hostname changes on restart — always copy it from here.
—
Endpoints
Add whichever surface you need as a custom connector in claude.ai.
Claude Code
—
Observability
Live activity
MCP calls, Zoom API calls, OAuth, and webhooks.
Nothing yet.
Pick a tool.
Live traffic
Waiting…
Admin
System administration.
Anthropic API key
Powers the Two Paths tab — Claude runs the MCP tools server-side.
Stored AES-256-GCM encrypted, never sent back to the browser.
- Status
- —
- Model
- —
Users
Who can sign in to this console.