Claude can work inside your ZoomSphere workspace directly through MCP (Model Context Protocol): it does not hand you text to copy somewhere, it puts the post in your calendar and reads your real numbers. ZoomSphere is listed in Claude's official connector directory, so connecting it takes about two minutes: find it, click Connect, sign in.
Fastest way: open claude.ai/customize/connectors/id/zoomsphere while signed in to Claude and jump to Step 2.
Team or Enterprise member? If your Owner has already added ZoomSphere for the organization, see Claude for Teams: rolling out ZoomSphere to your organization, Part 2.
Added ZoomSphere by hand during early access? See Moving from the early-access custom connector.
What you will need
A ZoomSphere account with access to the workspaces you want Claude to work in. Claude will only ever see what that account can see.
A Claude account (Free, Pro, Max, Team or Enterprise), on claude.ai in a browser or in the Claude desktop app.
About two minutes. No API keys, no server address to type.
Step 1: Find ZoomSphere in the directory
In a browser (claude.ai)
Click your name in the bottom-left corner of the sidebar, then Settings.
In the left sidebar, find the group called Customize and click Connectors.
Select the Discover tab, type ZoomSphere into the search box and click the ZoomSphere card.
Markers 1, 2, 3: the Discover tab, the search box, the ZoomSphere card. A green check on the card means you are already connected.
In the Claude desktop app
Click Customize in the left sidebar.
Select the Connectors tab, then Discover.
Search for ZoomSphere and click the card. From here the app shows the same screens as the browser.
Step 2: Click Connect
The ZoomSphere page shows what the connector does, the full list of tools and the server address. Click Connect in the top-right corner.
The ZoomSphere page in Claude's directory. Here it is already connected; before you connect, the button reads Connect.
What the Community badge means: Claude marks connectors built by the company behind the product as Community. ZoomSphere's connector has passed Anthropic's automated review and is built and operated by ZoomSphere itself. Claude shows the same notice for every Community connector.
Nothing happened after Connect? Pop-up blockers are the usual culprit. Allow pop-ups for claude.ai, then click Connect again.
Step 3: Sign in to ZoomSphere and allow access
Claude takes you to app.zoomsphere.com. If you are not signed in there, log in with your normal ZoomSphere account. Then you get the authorization screen.
The ZoomSphere authorization screen. Served by ZoomSphere, not by Claude: the address bar must read app.zoomsphere.com.
Check three things, then click Allow Access:
Redirects to https://claude.ai/api/mcp/auth_callback and nothing else.
Permissions: "Access and manage your ZoomSphere data through MCP". Read and write, with your own account's rights.
Signed in as: check that it is you, and the right ZoomSphere account. This is the identity Claude will act under.
Step 4: Check that it says connected
You land back in Claude with a small "Connected to ZoomSphere" message. The ZoomSphere page now shows Connected, and on the Yours tab the ZoomSphere row shows Individual under Authorization and a check mark under Status.
Step 5: Decide what Claude may do without asking
On the Yours tab, click the ZoomSphere row. Under Tool permissions every tool is listed, split into Read-only tools and Write/delete tools. The dropdown on the right of a group sets every tool in that group at once; the three icons on a row set that one tool.
Tool permissions. Marker 1: group dropdown. Marker 2: per-tool icons.
Always allow: Claude uses the tool without asking. Sensible for read-only tools.
Needs approval: Claude stops and asks you every time. This is the default.
Blocked: Claude cannot use the tool at all.
A good starting point: set Read-only tools to Always allow and leave Write/delete tools on Needs approval. Claude can then answer questions about your calendar and analytics freely, and still has to ask before it creates, changes or deletes anything.
Planning scheduled tasks? A task runs with nobody watching, so a tool on Needs approval makes it wait for a click that never comes. Set the tools the task needs to Always allow, and block anything you never want it to do. More in How to put your social media on autopilot.
Step 6: Switch it on in your chat
Connecting the account is not the same as using it in a conversation. These switches are per chat, so a brand new chat may start without ZoomSphere.
In any chat, click the + button at the left end of the message box.
Click Connectors.
Switch ZoomSphere on.
The + menu. Markers 1, 2, 3: Connectors, the connector list, ZoomSphere. The desktop app looks the same, a couple of labels differ.
Step 7: Try it
Start with something read-only, so you can see it really is talking to your workspace:
"What ZoomSphere channels do I have connected, and what is scheduled for next week?"
"Draft three LinkedIn posts about our new pricing and put them in ZoomSphere as ideas."
"How did our posts perform last month compared with the month before?"
"Schedule the approved carousel for Thursday 9:00 on Instagram and LinkedIn."
If you left write tools on Needs approval, Claude stops before the first one and asks. Read what it is about to do, then allow it. More than 30 ready prompts are in the ZoomSphere MCP prompt library.
What Claude can do with ZoomSphere
Create and schedule posts: Create Post, Update Post, Delete Post, Get Post Job Status
Read what is planned: List Posts, Get Post, Get Posts Preview, Get Scheduling Context
Respect each network's rules: Get Post Type Options, Get Post Type Rules
Work with Ideas: List Ideas, Create Idea, Update Idea, Delete Idea
Attach media: Upload Direct, Upload From Url, Upload By User, Get Upload Status
Read analytics and build reports: Get Posts Analytics, Get Posts Analytics Summary, Get Post Analytics By Ids, Get Channel Analytics, Get Channel Analytics Summary, List Metrics
Tell us what is broken: Send Feedback
Managing the connector later
Open ZoomSphere on the Yours tab. Disconnect signs you out but keeps the connector. The three dots next to it hold Refresh tools list (use it whenever we announce a new tool) and Remove, which deletes the connector from your account.
Claude Code and other MCP clients do not use the directory. Add the server address https://mcp.zoomsphere.com/mcp there, for example in Claude Code: claude mcp add --transport http zoomsphere https://mcp.zoomsphere.com/mcp, then run /mcp to sign in.
Something not working? See ZoomSphere MCP: troubleshooting and security. Want to know what you can do once connected? See Getting started with ZoomSphere MCP.