> ## 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. > ## Agent Instructions > For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project. > Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up. > Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md > Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md. # Get started with OpenWork Cloud > Connect the desktop app to your organization for shared skills and plugins, managed connections, models, policies, and hosted workspaces OpenWork Cloud # Bring OpenWork to your team. Share skills, connections, policies, and workflows while keeping access under your control. [Open in browser](https://app.openworklabs.com/) [Team quickstart](https://openworklabs.com/docs/cloud/team-quickstart.md) > [!NOTE] > > OpenWork Cloud is optional. The local desktop app stays free, requires no Cloud sign-in, and supports your own providers, skills, plugins, and custom MCP servers. Use Cloud when an organization needs to assign and manage those resources for a team. OpenWork Cloud is available at [app.openworklabs.com](https://app.openworklabs.com/). It is for teams that want shared identity, shared skills and plugins, managed connections and models, desktop policies, or hosted workspaces. First, create or join an organization and connect the desktop app to it. ![OpenWork Cloud org settings with organization identity, allowed email domains, and allowed desktop versions](https://mintcdn.com/differentai/0I0ZjSLCXFqgrauv/images/cloud-org-settings.png?fit=max\&auto=format\&n=0I0ZjSLCXFqgrauv\&q=85\&s=49a5842dd0cb6ab856fab191b5d9e13d) 1. Open [app.openworklabs.com](https://app.openworklabs.com/) in your browser. 2. Follow the setup steps to name your organization and choose a starting point. 3. Finish checkout if OpenWork Cloud asks for billing. 4. Continue to the desktop sign-in steps below. Once you're there, you can configure the settings for the organization. ## Configure org settings > [!NOTE] > > Only the organization owner can change these settings. 1. In the cloud app, open **Settings › General** (the [Org settings page](https://app.openworklabs.com/dashboard/org-settings)). 2. Set the name for your organization. 3. Optional: enable **Restrict allowed email domains** and add the approved domains. 4. Optional: under **Allowed Desktop Versions**, choose which desktop app versions can sign in to the organization. These settings apply across the organization. You can also create teams, share plugins and skills, configure Connectors and shared models, and deploy hosted workspaces. Next, you want to make sure you can sign in the desktop app. ## Sign in from the desktop app 1. Open **Settings › Account**. 2. Click **Sign in**. 3. Finish sign-in in your browser. 4. If the browser does not return to OpenWork automatically, click **Paste sign-in code**, paste the `openwork://den-auth?...` link or one-time code from OpenWork Cloud, then click **Finish sign-in**. ## Cloud URL used by the desktop app The desktop app uses a single Cloud URL: the Den web `baseUrl`. The hosted default is `https://app.openworklabs.com`. All Cloud API and MCP traffic is derived from that one URL through the web app proxy: * Cloud API requests go to `/api/den/v1/...`. * OpenWork Cloud MCP requests go to `/api/den/mcp/...`. The desktop app does not store or read a separate API URL. On startup it reads the Cloud URL from `desktop-bootstrap.json`; if that file is missing, it falls back to `https://app.openworklabs.com`. When you change the Cloud URL in **Settings › Account**, OpenWork writes the new `baseUrl` back to the bootstrap file so the next launch uses the same source of truth. ## Choose your organization After sign-in, pick your organization in **Settings › Account**. Plugins and skills shared with you appear in **Settings › Library**, under **From OpenWork**. ## What to do next * Send members to [Connect your services](https://openworklabs.com/docs/start-here/connect-your-stack/connect-services.md) to sign in to team-approved accounts from the desktop app. * Use [Connectors](https://openworklabs.com/docs/cloud/share-with-your-team/shared-mcp-connections.md) to publish a managed service and grant member or team access. * Use [Publish and copy a skill](https://openworklabs.com/docs/start-here/do-work-with-it/publish-and-copy-a-skill.md) to share a skill or plugin with people or teams, or [Collections](https://openworklabs.com/docs/cloud/share-with-your-team/collections.md) to group several plugins for the same audience. * Use [OpenWork Web](https://openworklabs.com/docs/cloud/run-in-the-cloud/shared-workspace.md) to give members a hosted OpenWork workspace in the browser, with nothing to install. * Use [LLM providers](https://openworklabs.com/docs/cloud/share-with-your-team/managed-llm-provider.md) or [custom LLM providers](https://openworklabs.com/docs/cloud/share-with-your-team/custom-llm-provider.md) to manage shared model access. * Use [Members and RBAC](https://openworklabs.com/docs/cloud/members-and-rbac.md) to invite people, create teams, and control access. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.