> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sharing MCP connections with your team
> Share Notion, Linear, Stripe, Exa, or any MCP server in OpenWork Cloud with Individual accounts by default, or One org account when everyone should act as the same account
Use `MCP Connections` when you want the org to manage an MCP integration once
— the server URL, who can use it, and how people sign in — instead of every
member configuring Notion or Linear by hand on every machine.
Two ways to handle whose account the AI uses, chosen per connection:
* **Individual accounts** — each person signs in as themselves. This is now
the default for OAuth servers, and it fits tools like Notion or Linear where
people have their own pages, projects, and permissions. The agent acts as
*you*, and the provider's own access rules apply.
* **One org account** — an admin signs in once (a bot, service account, or API
key). Every granted member's AI acts as that identity.
## Publish the connection in OpenWork Cloud
1. Open `MCP Connections` in the OpenWork Cloud dashboard.
2. Click `Add Connection`.
3. Pick a preset (Notion, Linear, Stripe, Sentry, Exa, Context7) or enter any
MCP server URL.
4. Choose the account mode: `Individual accounts` or `One org account`.
5. Choose who can use it: the whole workspace, specific teams, or specific
people.
6. Click `Create`.
For a One org account connection, finish by clicking `Connect` and completing
the provider's sign-in as the org account. Individual accounts connections are
ready to publish immediately — each person connects themselves.
On `Your Connections`, an unconnected One org account connection shows
`Waiting for an admin to connect` to members. Workspace owners and admins get a
`Connect` button on that row so they can finish the org account sign-in there.
## Slack
Slack's MCP server requires a pre-registered Slack OAuth app.
1. Create or open a Slack app in [Slack API apps](https://api.slack.com/apps).
2. In OpenWork Cloud, add the Slack connection and paste the app's client ID
and client secret.
3. Copy the OAuth redirect URL OpenWork shows after creating the connection,
then add it to the Slack app's `OAuth & Permissions` redirect URLs.
4. Members open `Your Connections` and connect their own Slack account.
For the local desktop-only setup, see
[Connect Slack MCP](/start-here/connect-your-stack/connect-slack-mcp).
## What members see in the desktop app
Granted members find the connection in `Settings -> Extensions`, in the same
catalog as everything else the org shares:
* **Marketplace tab** — connections you can use but haven't connected yet,
with a `Connect your account` action.
* **My Extensions tab** — connections that are ready: ones you've connected,
and One org account connections your admin manages.
## Connect your account
1. Open `Settings -> Extensions -> Marketplace`.
2. Click the connection card, then `Connect your account`.
3. Your browser opens the provider's own sign-in page. Approve access.
4. The browser shows `Connected` — return to OpenWork.
5. The card updates by itself, no reload needed, and moves to
`My Extensions`.
Your sign-in is stored in OpenWork Cloud, not on this machine — connect once
and every device you use is connected.
## Your agent can use it immediately
No restart, no resync. Ask for something the tool can do:
> Find the "Q3 launch" page in Notion and summarize it.
The agent discovers the org's tools through the `OpenWork Cloud Control`
connection, and executes them with **your** account — your permissions,
your audit trail on the provider's side.
If the agent finds a tool you haven't connected yet, it tells you in the
chat with a `Connect` button — you never have to go hunting in settings.
## Notes for admins
* Members only see connections they've been granted — access is explicit
(workspace-wide, team, or per-person), and it's enforced by the server on
every request, not by the app.
* Removing a connection (or a member's access) takes effect immediately for
every device.
* Members who already connected a tool directly in their desktop app keep
their existing setup — publishing an org connection never removes or
changes anyone's local configuration.
## Relationship to local MCP servers
Everything in [Add an MCP server](/start-here/connect-your-stack/add-an-mcp-server)
still works, with or without a cloud account. Local servers (like OpenWork
Browser and UI Control) always run on your machine. Org connections are for
the things a team shares.