Zoom

Each member connects their own Zoom account. Through Zoom's MCP server, their OpenCode can then:

• Search their meetings by topic, person or date, and schedule, update or cancel meetings when asked.
• Read what a meeting left behind: AI summaries, transcripts, next steps, shared docs and cloud recordings.
• Create and export Zoom Docs, such as meeting follow-ups, manage their collaborators, and use Zoom Hub files.
• Read their Zoom notes, and search or ask questions across their Zoom content.

OpenCode sees only what the member's own Zoom account can see.

• An OpenCode Console workspace with Integrations. Integrations is in early access: if your workspace doesn't have an Integrations tab yet, email help@anoma.ly.
• An owner or admin of the workspace to add Zoom. Members can't add integrations.
• A Zoom account for each member who connects. Your Zoom admin may need to approve the app first, and summaries, transcripts, Docs, Hub, notes and asking questions depend on your Zoom plan and AI Companion settings.
• Each member's OpenCode signed in to Console, as Connect OpenCode in Console shows.

If you're an owner or admin and your workspace doesn't show Integrations yet, email help@anoma.ly to have it turned on.

1. An owner or admin opens Integrations in Console and clicks Connect on Zoom, or uses Connect Zoom at the top of this page.
2. They don't choose whose accounts it uses: each member connects their own Zoom account, and there's no shared workspace account.
3. They sign in to Zoom and approve the access OpenCode asks for.
4. Each member then opens Zoom in Integrations and clicks Connect to sign in. If their OpenCode tries Zoom before they have, it tells them where to connect.

Once a member connects, Zoom appears in their OpenCode. Anyone can leave it out of their own OpenCode with Include in your OpenCode config on its page.

Console stores each sign-in's access and refresh tokens, encrypted, and sends them only to Zoom. It also keeps your Zoom user ID from the token, only to act on Zoom's notice that you removed the app. It doesn't look up your Zoom profile. It also records the tools Zoom lists (their names, descriptions and inputs) and its instructions for agents, so admins can review them.

Ask OpenCode in your own words. For example:

• What did we decide in yesterday's design review? List the next steps.
• Find last week's meetings about the billing migration and summarize the open questions.
• Turn today's standup notes into a follow-up doc in Zoom.

OpenCode reaches Zoom through Console, which adds your credentials on the way, so your OpenCode never holds them. Results go back to your OpenCode, which passes them to the model it's using. Console logs each call (the integration, the tool, whether it was allowed and whose account it used) but never what was sent or returned.

Owners and admins review Zoom's tools on its page in Integrations and can turn any of them off. By default, a tool Zoom adds or changes stays hidden from OpenCode until an owner or admin approves it. Rules in Controls decide who can use Zoom, and can limit it to tools that only read.

Disconnect your account

Open Zoom in Integrations and click Disconnect. Console deletes its copy of your Zoom tokens and any sign-in you had started, and asks Zoom to revoke OpenCode's access. When someone leaves the workspace or is removed from it, Console deletes the accounts they connected for themselves the same way.

Remove Zoom from the workspace

An owner or admin opens Zoom in Integrations and chooses Remove… from the … menu. Console deletes Zoom from the workspace with every account connected to it, the tools it recorded, its settings and members' choices, and asks Zoom to revoke each account's access. Disable… in the same menu turns it off for everyone instead and keeps all of that until it's turned back on.

Remove the app in Zoom

You can also remove the app on Zoom's side: Sign in to the Zoom App Marketplace, click Manage, then Added Apps, and click Remove next to OpenCode. Zoom then tells Console, which deletes your tokens in every workspace you connected.

• Console keeps each Zoom sign-in's tokens encrypted and sends them only to Zoom, never to OpenCode.
• It records the tools and instructions Zoom lists, so admins can review them. It doesn't look up your profile: the one detail about you it keeps is your Zoom user ID from the token, to act on Zoom's notice that you removed the app.
• It logs each tool call (who made it, the integration, the tool, the outcome and timing) for 30 days, never what was sent or returned, and doesn't keep tool results.
• Results reach your OpenCode and the model it's using.

The privacy policy explains how Anomaly handles personal data, and the terms of service cover using OpenCode. To ask for a copy of your data or for it to be deleted, email help@anoma.ly.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays), and you don't need an account. The support page covers data requests, security reports and more.