Fewer Clicks, Same Permissions: Connect an Assistant to Your Workspace
Managing a shared workspace means repeating the same tasks: checking a time slot, creating a booking, finding a client, or preparing an announcement. The back office handles these well, but it’s not always the fastest way to ask in plain language.
Cowork. offers an MCP module for this. MCP (Model Context Protocol) is an open protocol: your assistant—Cursor, Claude Desktop, or another compatible client—calls your workspace’s actions directly, instead of guessing from an export or copy-paste.
The assistant doesn’t have “magic admin” access. It connects with your account and can only perform actions your account already has permission to do.
What It’s For, Concretely
You keep Cowork. as your single source of truth. The assistant becomes another entry point, useful when asking a question is simpler than clicking.
Some typical requests:
“Which resources are available Tuesday morning?”
“Create a booking for this client on this time slot.”
“List bookings pending validation.”
“Summarize the workspace’s recent activity.”
The response follows the same rules as the back office: availability, roles, and only your workspace’s data.
What Each Role Can Request
The module mirrors the three existing roles. Switching assistants doesn’t change permissions.
The manager oversees operations: spaces and resources (pricing, closures, booking domains), bookings, clients, categories, promo codes, team, dashboard, payments, smart locks, subscription plans, events, billing exports, directory listings, notifications, and support tickets.
The collaborator views activity—spaces, bookings, clients, dashboard, events, subscriptions—and can post announcements. They don’t perform manager-only actions.
The member stays within their own account: their bookings, favorites, and availability alerts. They don’t see other clients or workspace settings.
A platform admin account isn’t needed to connect this module. The connection is made with a workspace account.
Your Data Stays in Your Workspace
The connection is authorized through your browser. You see the client requesting access and can approve or deny it. No passwords are pasted into the assistant’s configuration.
Three safeguards:
The role. The assistant can’t unlock actions your account doesn’t already have.
The workspace. It doesn’t access data from another location, even if you manage multiple spaces.
Revocation. From the same settings page, you can remove a client, and their access stops immediately.
The module is available based on your plan. If it’s not included, the connection page won’t appear, and authorization is denied.
How to Connect It
In the back office, go to Settings, then Connect My Assistant.
Copy the provided block for Cursor or Claude Desktop.
On first use, authorize access on the consent page.
To disconnect an assistant, revoke its client on the same page.
Some actions remain in the interface: file uploads, smart lock connection flows in the browser, and anything related to platform administration.
What’s Next
The module aligns with your workspace’s features: when an action exists for your role in Cowork., it’s designed to be accessible the same way through your assistant.
Want to enable it for your plan or verify that a connected client has the correct permissions?
Contact us or open Connect My Assistant in your workspace settings.